JIRA Sucks, But Iâve Got You
JIRA lags, JIRA lies,
JIRA makes me want to cry.
Click a buttonâwait and pray,
Maybe it will load today.
Sprint is stuck, workflowâs dead,
Tickets haunt me in my head.
Epics, subtasksâwhat a joke,
Burn it all and watch the smoke.
But donât despair, there is a way,
To make this pain just go away.
Iâve got videosâwatch and see,
A better world, where JIRAâs free!
Tired of JIRA? Watch my YouTube videos and take back your sanity!
Yeah, but despite its awfulness, Jira is not as bad as our clients who insist we report issues in Trello. Itâs difficult to think of a less appropriate application to use for bug tracking. PhotoShop, perhaps, but even then Iâm not sure.
Maybe the key away from the hate is shifting left enough so that tracking bugs is no longer a necessity? Helped me with my hate of Jira back in the days. Use that feeling as a force for change.
No, I do not.
I and many others Iâve worked with try to avoid using it as much as we can.
We find alternative ways of expressing ourselves, communicate, white-board drawings/diagrams/lists, notebooks, post-its, wikis, spec files, and more.
Donât feed Jira with too much stuff, as it might eat up your time later.
My biggest problem is not Jira itself, but how people are using it.
Using it for command & control sucks.
Having trustful relations with people makes working with Jira enjoyable ⊠erm ⊠acceptable.
Jira has some heavy issues, but I have workarounds for then. (Donât try to edit ticket descriptions in parallel)
But what really sucks is people just relying on the Jira workflow instead of talking to each other.
I donât have issues with jira since i can now how to work with it. The only issue I have is the way ticket hierarchy works inside a sprint. I think there could be a better way to display user stories whilst allowing their sub tasks to be included in separate sprints.
For the kanban board, its good.
The problem in my team is people trying to use it as it suits them instead of a unified approach. The âI donât like thisâ crowd makes jira useless.
I actually disagree that JIRA is all bad
While it does have its quirks, JIRA is a lifesaver for many complex projects, providing excellent visiblity, tracking and collaboration, especially in Agile.
Yes, it sometimes feel slow but thatâs often due to misconfiguration or overly complicated workflows.
Jira is fine, I havenât seen anything better, but if you donât need all its features and complexity, maybe you can use something simpler. But anyway, even in a small team with a simple project, itâs a nice tool for tracking tickets. So, the issue is probably not with Jira but with someoneâs inability to use it properly
That depends on the perspective no?
Iâve had a couple of times it being âset properlyâ according to someone, but it was bad for most of the people using it.
Anyway, itâs not about Jira per se but about how people use it. If someone is forced to use it in a way that makes it painful, itâs not Jiraâs fault
I love Jira when time management plugin is there as I can easily maintain what i did whole day instead of memorizing what i did and i didnât.
Another benefit of jira is number of other plugins like Xray Zephyr Squad, etc.
So using Jira as a standalone product might be boring or not upto the mark but when correct plugin are integrated and used in correct way then Jira is helpful.
Their AI Summary feature has not been so much helpful but it is not bad either.
I used to hate it, with a passion, but then I grew past it when I realised that it is just a tool. Others have mentioned that its usually not the tool but the way its implemented, but I think of it as a half baked solution that once you get doing something working it will work for you.
Thereâs weirdness though, like how you canât export docs in Confluence (can export pdfs, but not doc files). Or how there isnât a standard approach to custom fields and regular fields for issues. Or that they go off on rebranding and repainting etc, when what I want is for it to not take an age to load when Iâm screensharing.
I actually like Jira - A common phrase I use, is 'âIf the issue you speak of is not in Jira, it does not existâ - Frustrating to many, but its only as good as the information you put into it
Why canât I change the assignment of a commit to an issue like in Fisheye???
Typos in issue numbers of commit messages happen. And itâs not the thing you want to rewrite your branch history for.