02-24-2013 04:06 AM
Garett,
When you read this please report these issues, I struggle to use Jira as the autocomplete boxes fail to do so, making it impossible to autocomplete, I have to hunt around for a similer issue and then cut and paste across.
Anyway;
- Linebreaks are not handled on a browser
- screenshots submitted as landscape are doubled up
- the only way to click through to an app is through its image please do it through the app title as well
02-24-2013 08:38 AM
02-25-2013 01:30 PM - edited 02-25-2013 01:33 PM
Thanks Garett.
I think the critical words there were 'when working'.
If JIRA is a pain to use even when it does work and people are complaining it is taking months to get a response from the vendor support form, I'm still waiting for a critical one that has forced me to remove one of my apps for PlayBook from BlackBerry World (luckily its not revenue bearing).
Then it can be no surprise that bugs will go unreported.
On this one though it would have been nice to see it being fixed pro-actively as it affected all your developers.
Are there just no more people left in your marketing and quality control to spot these things?
I'll accept your posting as the answer once I see it fixed.
02-25-2013 01:37 PM - edited 02-25-2013 01:37 PM
BBSJdev wrote:
On this one though it would have been nice to see it being fixed pro-actively as it affected all your developers.
That's definitely the ideal situation, but things get missed/bugs happen in any system. In this case it is a bit more apparent being the formatting is not respecting line breaks, so I completely understand the frustration.
I am working with the BlackBerry World folks on this issue and will keep the thread apprised with details as they become available.
02-25-2013 02:28 PM
02-25-2013 09:52 PM
jtegen, why dont you submit a request for this in JIRA. ![]()
Seriously though, I have to agree, one site, one password for everything developer related.
03-14-2013 07:28 AM
Come on guys, 3 weeks now, can we get a status update on this one as well?
03-15-2013 04:27 PM
indeed... ![]()
03-19-2013 03:34 PM
Status update: It's now fixed ![]()
http://devblog.blackberry.com/2013/03/blackberry-w
03-19-2013 06:34 PM