What are some alternatives to JIRA? Also, how much of the hate directed towards JIRA buried resentment towards Agile and other project management paradigms?
It's a joy to use
51–60 of 539 posts
What are some alternatives to JIRA? Also, how much of the hate directed towards JIRA buried resentment towards Agile and other project management paradigms?
It's a joy to use
The real problem with Jira is that every company adopts it without sufficient support. It needs dedicated admins. You can't just let every single team YOLO things. Unfortunately, what happens is a company adopts it from the start, and then it grows into an impossible-to-use forest where there's no meaningful way to bring things back to actually usable, and everyone is miserable.
If a tool needs this level of support it's not a good tool and not even a tool - it's the no-code equivalent of a framework. I'd rather pick any other ticketing system which has things done in one way than waste my life configuring jira
You can either have something incredibly powerful, like Jira, with a lot of sharp edges, or you can use something incredibly similar. The latter would be more like 'no-code' since it's going to be drastically limited in terms of adapting to how your business does work, versus Jira which can be transformed into just about anything.
That 'just about anything' is the root of the problem, since over years a business will let dozens of people alter configurations and do special little bespoke things on their projects until it's unsustainable.
That said, which competitor has a visual workflow editor, to which I can add custom statuses/transitions, which are applied based on various conditions/validations? And custom screen/field configurations? And custom resolutions? And time tracking? And apply security/permission schemes across all these things?
I get it, Jira sucks, I agree, but what's the go-to competitor?
The real problem with Jira is that every company adopts it without sufficient support. It needs dedicated admins. You can't just let every single team YOLO things. Unfortunately, what happens is a company adopts it from the start, and then it grows into an impossible-to-use forest where there's no meaningful way to bring things back to actually usable, and everyone is miserable.
Dedicated admins make it even worse, because they have the bandwidth and inclination to do all kinds of crazy customization, which is what takes jira from merely bad to terrible. The worst jira instances I've ever seen are the ones that had full-time people customizing them.
I wish the comments were more specific about which features they don’t like. For me a particularly frustrating aspect is the way the UI moves around a lot. I’m quite anxious to click anything until all the loading spinners have stopped in case I click the wrong thing. Then I could be taken to a page or feature I’ve never seen before. Also it’s really annoying when I try to copy something from a ticket description but…
on edit: once you have a query you like save it as a personal filter and it will show up somewhere in the UI, because Jira sucks who knows where (changes all the time), but you can of course also make personalized dashboards and place the filters you have made on to that dashboard with a widget that runs the filter.
on second edit: evidently I earned someone's downvote by not being adequately anti-jira despite having put in that Jira sucks, but really the comment to which I'm replying ends with:
" I'd also like to add that as a developer, once I finish my ticket I assign it to a QA. Then I can never get back to the ticket. I'd like a really easy way to see all of the tickets I've ever completed. But completed tickets aren't assigned to me, they're assigned to QA. "
which, using JQL, is real easy.
I'm sometimes kind of surprised at how often I see people say they don't mind it. It's by far the tool I like the least out of everything I've used at any job I've ever been in.
It's a tool for the boring part of software engineering- I don't expect it to spark joy. I wish it were faster, scaled the full width of my monitor, allowed external editors, etc. Overall it gets the job done well. Everything else that I've used is horrible which makes it the best in my experience but that's still not saying much.
I'm going to stick up for Jira. I certainly don't "love" Jira, though I do think they've made significant improvements with "new Jira" (I think they call them team-managed projects now).
The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for the extreme difficulty of the organization-wide problem Jira is trying to solve. It's always taken on from the position of "well, it didn't make my specific use case easy", but never with an appreciation with some of the complexity that Jira needs to solve for other users at your company, never mind other companies.
Obviously some of the complaints (speed, stability) are very valid, but here's a question I think is just as valid: why don't you think some other company has come along and toppled the Jira crown? Certainly tons of them have tried, and while many have their supporters, they are almost equally likely to have their detractors.
The fact is, building a generic project management and tracking tool is a really difficult, hard problem. In my old age as a programmer I feel like Jira is kind of like our form of government: "Jira is the worst project management tool, except for all the others".
Earlier quoted context omitted.
If a tool needs this level of support it's not a good tool and not even a tool - it's the no-code equivalent of a framework. I'd rather pick any other ticketing system which has things done in one way than waste my life configuring jira
Just about every enterprise tool requires a proper implementation and system admins and business process analysis and change management to get setup. A lot of enterprise tools are "crap, why would the company ever use this", and 90% of that is in the implementation (or lack thereof)
I feel like hating on Jira is the pastime that is now passed down from each generation of programmers to the next. I'm going to stick up for Jira. I certainly don't "love" Jira, though I do think they've made significant improvements with "new Jira" (I think they call them team-managed projects now). The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for…