4 ms·
I was a JIRA admin for a number of years for an organization that had a heavy QA workflow. It was all about making sure that every issue had an "owner," at any
by ChrisMarshallNY 6y ago
I was a JIRA admin for a number of years for an organization that had a heavy QA workflow. It was all about making sure that every issue had an "owner," at any given time, a strict approval and verification process was followed, and that as much up-front data as possible was collected during the initial report.
In my experience, unless the people entering the issues are paid, professional engineers, we'll never get the information we need up front.
I have found that the basic GitHub model works well for me.
When someone reports a bug, they are doing me a favor. It's in my interest to ensure there are as few roadblocks as possible to them sending a report. If they give contact info, then I can contact them with specific questions.
In my experience, a simple email form is the best way to solicit reports. It may have a workflow hidden behind it, but I have found that the simpler the workflow is, the more likely it is that the issue tracking will work.
JIRA basically starts off complicated, and it's possible to make it much, much worse.
It's also slow, but that wasn't really the problem we had. The workflows and forms were where it fell down for us.
- jnwatson 6y agoIn my experience, it isn't Jira that people hate, it is the horrible rules and bureaucracy-ridden workflows that Jira allows an admin to implement. My team switched back to Jira after trying several other tools and we're pretty happy.
- Twirrim 6y agoAll the extra plugins etc. that people bolt in to get those extra features really slow it down too.
- _Qeomash_ 6y agoAs a current Jira admin, I constantly have to fight this. A non dev team came into Jira and implemented a huge octopus of a workflow (despite my strong advice against it) and were shocked to find out it didn't really help them work better. The handful of teams inside that department that I've gotten to switch over to a simpler To Do / In Progress / Done style workflow have been much happier. Jira has many, many faults, but most of them are what the users do to themselves.
- gpm 6y agoIn my experience, it's both. Jira is laggy as fuck and makes every interaction I have with it take 5 times as long as it needs to, or at least it has been in the two organizations that I've worked for that used it.
- hinkley 6y agoIf you turn bureaucrats into UI designers, you’re gonna have a bad time. We have several classes of tooling that do just that. Atlassian tools are particularly overt in their belief that the tool belongs to the managers and not the team. Bamboo especially.
- regularfry 6y agoWe're in what I tend to think of as Jira's pit of despair: there's no explicit support for the on-prem instance; workflow configuration regularly seems to go wrong and has a wide blast radius when it does; nobody trusts the data so we don't get any useful reporting out of it; the UI is... not exactly slow, but I wouldn't call it snappy either; and there's no money for addons that would genuinely help us. Github Projects would be absolutely fine for us, but we can't switch out because Jira is "what everyone uses" and "has more features", despite us not really using any of them.
- einpoklum 6y agoI also don't like JIRA itself, it feels bloated from the get-go.