As a generic ticket tracking system with support for project planning and sprint tracking, it's great for small to mid-size companies and even many larger companies that don't have the know how or funding for project management tools.
-
Ever wanted an RSS feed of all your favorite gaming news sites? Go check out our new Gaming Headlines feed! Read more about it here.
-
We have made minor adjustments to how the search bar works on ResetEra. You can read about the changes here.
What's your thought on Atlassian JIRA?
- Thread starter DiipuSurotu
- Start date
- Tech/Gadgets
It gets the job done, as a QA Engineer it is better than the other tools I've used before it. Just gotta make sure the flows and processes are all good.
Pet peeve is devs not wanting to engage with it, ignoring the flows or asking me to add bugs for them. Bro, you're a web developer not God crafting the 10 commandments, learn how to use the tool and write up a proper bug report yourself.
Also this gave me a chuckle during the pandemic.
Pet peeve is devs not wanting to engage with it, ignoring the flows or asking me to add bugs for them. Bro, you're a web developer not God crafting the 10 commandments, learn how to use the tool and write up a proper bug report yourself.
Also this gave me a chuckle during the pandemic.
It's a great tool, unfortunately every company I've worked at didn't have a dedicated Jira person, it was always a side-task for some support team leader or an admin, and it was always configured badly and full of obsolete bullshit that a full-time Jira admin would have solved in a week.
I used it in a highly regulated environment and it was basically a reporting tool not a project management tool. Quality team owned the entire process of how we could use it and it was absolutely garbage process that didn't provide any usefulness to how we planned and built software. In fact I would suggest the way it had been set up was actively harmful/dangerous to how we delivered features and had the opposite effect of what was the supposed remit of the quality team.
"What do you mean, 'I can't manually update my Resolution status'?!?
My work is complete, ticket's closed, and the resolution will forever be Unresolved?"
My work is complete, ticket's closed, and the resolution will forever be Unresolved?"
OP
OP
This just means the JIRA project (or the whole instance) wasn't configured properly
JIRA is terrible!
It's also infinitely better than almost every alternative, especially something developed internally. And it's flexible enough that a dedicated JIRA engineer can turn it into something not-terrible.
But it's also terrible that making it useable takes a full-time, dedicated engineer.
And even though it's better than 95% of the alternatives, the 5% that are better absolutely wipe the floor with it. Like, no matter what, JIRA will never catch up to YouTrack.
It's also infinitely better than almost every alternative, especially something developed internally. And it's flexible enough that a dedicated JIRA engineer can turn it into something not-terrible.
But it's also terrible that making it useable takes a full-time, dedicated engineer.
And even though it's better than 95% of the alternatives, the 5% that are better absolutely wipe the floor with it. Like, no matter what, JIRA will never catch up to YouTrack.
An engineer, and a dedicated PM to wrangle it, on top of the usual PM-y tasks
I just use it to report bugs and issues I've come across. I'm at a public transport company working on scheduling, run time analysis and calender management. The software we use is developed in Canada while we are based in Belgium. If there's issues I come across, I'll create a JIRA ticket and the support team in Canada will reply (eventually). It gets the job done.
I don't know if my work just hasn't upgraded or expanded what's possible in JIRA and Confluence but yeah, Confluence is a terrible experience. Editing using the CMS is whatever (barely functional at times) but my main complaint is that I can't access anything from a navigation standpoint.
My work uses it as an information hub for each department, but it seems like spaces are only "unlocked" after I've visited them from a link. I can't just click "HR" as an option and then go to "Benefits" it's only accessible via direct link. Once I've clicked that, maybe it will appear in my navigation bar. Is this a thing? Am I just frittering away in lonesome madness or is this how Confluence always works?
Definition of feature creep and over engineering that gets misused by teams all the time leading to it becoming a slow bloated mess
I have only used it so don't have much frame of reference, but my problems so far always seem to stem less from the tool and more from the higher ups changing the process every week. How they want things done changes so often that no one really knows how to use it or set up things, so we end up with a mess with awful signal to noise ratios and constant bitching about people not "using it correctly."
Out of the box it's so busted as to be useless. If you have dedicated Prod resources to customize and manage it it's unparalleled. But that makes it really hard to recommend
if a tool has to be meticulously set up and managed, perhaps the tool is not good? I've always hated the "you're not using it right" aspect people have with stuff like Jira.
I used Confluence at both jobs too and I can confirm it's worse then Jira.
I use JIRA all day honestly. I don't mind it whatsoever. We have so many sprints and fix versions on a monthly basis I really can't imagine us handling it any different. Also use confluence a lot too, but frankly I hate trying to format documentation on it. I don't think that's a knock on the software and just my inexperience using it for documentation creation.
OP
OP
I think you're looking at the "last visited spaces" menu, which is basically like a browser history (except with spaces instead of individual pages). That's not the menu where you can find the full list of spaces!
