21–25 of 25 posts
JIRA is that super shitty game that your girlfriend bought you, and you are going to get in trouble if you don't log a minimum number of hours of playtime. All the achievements in the world won't make it suck less.
But putting some gamification into a bug tracker is a good idea. For example, some kind of score/currency system that QA could spend to adjust priorities and put "bounties" on their favorite bugs, and programmers could "earn" by fixing those.
Earlier quoted context omitted.
I'm a developer. My time spent with Jira is an annoyance at best, or a hatred at worst. I can't change that. It's a good tool for our QA and PMs. Something like this is nice to distract me. I don't think that gamification is equivalent to treating you like a child. > "Gamification" of software can't possibly be the right thing to do I don't think you are qualified to make this decision for the rest of the world. If t…
"I'm a developer. My time spent with Jira is an annoyance at best, or a hatred at worst." I support that. Jira is a feature monster. It is aimed at producing nice pie charts, percentage numbers and lists (of solved, unsolved, analyzed etc. problems). A nice toy for managers. These are probably the people who make the buy decision, so it was clever to aim jiras features at this group instead of bothering with develope…
But I'm worried as I've read a few people on this thread say that JIRA is made for managers and not for developers. As the guy who was here from the beginning - I can say that it is definitely true that we made JIRA target managers - we found that too many people using Bugzilla spent all their time reporting status upwards, and if we could automate this, then developers could spend more time coding, and less time reporting.
But that doesn't mean it shouldn't be a great experience for developers. As someone who longs for the day that I can spend 10 hours coding (I'm now co-CEO, so I don't get to code as much anymore), I want JIRA to rock for this use-case.
But I'd love your feedback on where we need to improve. What is the 'inner loop' of JIRA usage for yourself? What functions do you do 20 times a day that we should make lightening fast?
I'd also love to know which version you are using. We've made some serious speed improvements in the last 12 months, as well as introducing keyboard shortcuts for the most common actions, so you can get around much faster than you used to. In JIRA versions >4.1 press '?' to get a list of shortcuts. My favourite is '.' when you are viewing an issue.
But seriously - would love your feedback. Or email me: scott@atlassian.com