“Jira is just a tool, there are plenty like it for helping break up large projects into small doable tasks. Which from my experience is helpful when you have multiple teams doing lots of things at the same time.”
“Jira/whatever-tool for agile practices was supposed to bring organisation and structure to help make engineering efficient. Instead it has taken over and now businesses act like engineers can't function without it.”
“Same thing with the 63 Jira fields. Every field on that form was added by a post-mortem where someone asked why we didn't know. No field has ever been added by a post-mortem asking why it takes nine minutes to file a ticket, because that pain has no incident report attached to it.”
“You’re now filling irrelevant stuff in jira because you don’t even understand what 50% of the jira fields mean because they’re irrelevant af all because jira admins tried to make a 1 size fits all type of tix.”
“You can look at metrics like the number of bugs and the length of time needed to fix them. Those numbers can inform decisions about how much time to devote to tech debt, refactoring, and process improvements.”
“Even though I'm not a big fan of Jira, I just tried it and couldn't make the hierarchy work. I've used trello before too but the list view (which is what I use the most) is basically non-existence.”
“My company a software company where i am working, has replaced jira by building an internal tool. I think its better that way, as eventually the company can create what they actually want, make changes on whatever they want, and eventually if they built a final product can also help other companies that has the same problem.”
“People who hate on Jira are the lucky ones that didn't have to use the worse options in the industry. The day to day operations are at fault, not the tool.”
“The good news is that with Jira MCP setup, most of those pain points can be completely eliminated. I haven't created a ticket through the Jira ticket form in a long time.”
“Jira fucking sucks, they're right, also, everyone atlassian project manager is a heroin addict... I have no idea why, but the stereotype is a stereotype.”
“As someone who has to manage Jira for devs, Jira is such a PITA. It's such a brittle piece of tech. Make one minor edit to a workflow and suddenly you've potentially orphaned thousands of tickets.”
“And that is the reason why i though "they will give you the code", because its open. There is plenty of open source ticketing systems out there, so i would just use that, idk why my boss decided on jira”
“Categorise every Jira Epic either Growth, Sustainability or Support. It’s an additional required field squads must fill out at ticket creation time and of course can be edited at any point.”
“We added a category field to Jira issues for things like feature work, bugs, maintenance, tech debt, etc., and captured approximate effort in hours. At the end of the quarter, I rolled it up and plotted the approximate percentages on a graph.”
“I don't do it in Jira at all. Menu bar app (Planim Time) with a JQL filter for everything assigned to me, I pin a couple of issues for the day and run the timer from there.”
“To distinguish the second and third bucket, you can use AI + Jira MCP / Rovo and add a label. You can then create jira dashboards and track the % of each bucket.”
“My Jira instance allows me to categorize everything we do as feature work, maintenance, bug fixes, etc. It makes it very easy to see how much we are spending on what. Maybe try that?”
“If you use JIRA, in your planning, you can have labels on your idea or epic cards. Intention is for roadmaps, engineering managers + product manager consciously have a certain percentage on build new vs run.”