Missing the ability to assign more than one person to a card.
Why Jira Sucks
401–410 of 530 posts
Re: Why Jira Sucks
#402Try linear.app and it will clarify why Jira sucks :)
It would be nice if any of the alternatives would be in line with Jira cost for a large enterprise. I can’t recommend this to anyone if our cost for issue tracking would quadruple overnight. Not to mention the migration costs...
Jira costs are going to skyrocket soon too since they are sunsetting Jira Server. Opportunity is ripe for competitors.
Re: Why Jira Sucks
#403Earlier quoted context omitted.
Do you prefer to... not have all the details in front of you for a task you're about to work on?
Generally as a senior dev part of your job description is to figure the details out. Not have them provided for you. As a jr or early mid level you can expect to have the majority of the details ironed out and nicely laid out for you to work on, but someone at some point had to actually figure it out and put it in the ticket. Whether that is you or someone else likely depends on your level, the stage of the company,…
> anyone who is downvoting this, please leave a comment with where you disagree. i'm unsure if i'm being received negatively on content or on tone
I would, but that's a detail that a senior dev like yourself should be able to figure out without people just providing it for you.
Re: Why Jira Sucks
#404To me, what sucks about JIRA (and would suck about any well-designed tool that replaces it) is not "feature x" but the entire JIRA mentality. All of it. It encourages micro-management. It encourages more and more process. It is the enemy of getting better at the DORA metrics, which requires streamlining process. tickets in JIRA are not the work itself, never was and never will be, it is a LARP of the work, but it get…
I work in the med-tech industry and Jira is a very good fit for that industry. Most compliance issues are solved by defining a way of working that uses a project management system like Jira. Someone else read how to label a product with CE-label and HIIPA, and all I have to do is report my work in Jira. Don't have to understand CE-labeling or HIIPA.
For compliance it must be possible to find who made a change, why they made that change, and how they validated and tested that change. In a heavily regulated industry like medical, it is very useful to have a tool like Jira when the audit comes up.
I still accept your point tough, if you need to go fast and break things (you know, innovate and prototype things), jira is a real blocker and the "jira mentality" slows things down, for better or worse.
Re: Why Jira Sucks
#405Earlier quoted context omitted.
A git commit is a "how," not a "what" or a "why." That's where JIRA comes in (if used properly). I don't love JIRA, but (IMHO) when it's used properly, it's a great tool.
A proper commit message should always have the ”why” (and, if necessary, the ”what”).
And even if it isn’t, how is it a developers job to explain why when there is a linked ticket in the commit message from product explaining it.
Re: Why Jira Sucks
#406Earlier quoted context omitted.
I disagree back, but at a different place. "who have to report progress and who are responsible for budgets." is the real problem. It's crazy that progress on engineering is measured in the number of tasks completed. This was one of the points of agile in the first place (to deliver user-stories, rather than engineering tasks) but it has mostly been lost since then, because people who are managing engineers don't kno…
Commercial artistic endeavors are deadly serious about schedules and coordination. Broadway and Hollywood have some of the most intense and impressive project management in the world. They couldn't survive without it. But it does look pretty different from tech project management. Department heads are not treated as task monkeys. They are treated as being potentially myopic about their own pieces of the puzzle, and g…
The appropriateness of different styles of planning is based largely on how much the work is labor vs knowledge-work. Programming disproportionately ends up being knowledge work, because everyone is always working in a language, framework, scale, or business area that they don't understand.
After all, programming is a craft that can have things akin to "writer's block" (for instance, being stuck on a bug or design). It's more like writing the script than shooting the movie.
Re: Why Jira Sucks
#407I aspire to build a product that has a website dedicated to how much it sucks, in namesake.
Re: Why Jira Sucks
#408I was a JIRA admin for a waterfall-based company (Japanese). They did process hard. Agile was a cussword, and the JIRA workflows were standalone engineering efforts; complete with custom JIRA plugins, written in Java, because even JIRA couldn't handle some of the process.
I guarantee that it would have had most of the folks here, whimpering under their standing desks.
It was the Tenth Circle of Hell.
It gave me a sort of PTSD, so that, now I'm on my own, I try not to write anything down, and, if I do, it's usually a small list on a whiteboard.
If I never see JIRA again, I will die a happy man.
That said, it is like blaming the asphalt for the eminent domain seizures for a road. It's a symptom.
Re: Why Jira Sucks
#409To me, what sucks about JIRA (and would suck about any well-designed tool that replaces it) is not "feature x" but the entire JIRA mentality. All of it. It encourages micro-management. It encourages more and more process. It is the enemy of getting better at the DORA metrics, which requires streamlining process. tickets in JIRA are not the work itself, never was and never will be, it is a LARP of the work, but it get…
I 100% disagree. Fixing a bug or delivering a feature where you haven't documented the process, (how the criteria were decided, when it was tested and deployed) is as good a running a web site nobody visits. JIRA hate comes from the bottom up. Developers don't like having to have their work parceled out so specifically. But it's not for them. It's for managers and stakeholders who have to report progress and who are…
> Fixing a bug or delivering a feature where you haven't documented the process, (how the criteria were decided, when it was tested and deployed) is as good a running a web site nobody visits.
This is patently false, as evidenced by every business in existence that doesn't use issue trackers, including most non-tech divisions of current businesses and most tech businesses until the rise of agile. And I question the value add of these things; my current company was built without them, and it's only as we've matured (well after the product was built and mostly refined) that issue tracking was used.
Re: Why Jira Sucks
#410Jira sucks but it's not because of these reasons. In fact if you fixed each item here, it would be worse. Jira sucks because it is unopinionated and infinitely customizable. As a result, everybody who believes they've discovered the perfect project management setup (spoiler: they haven't) is empowered to cook up their vision via an inscrutable set of customizations. This leads to a bunch of inconsistencies between pr…
Yeah, I've had really positive experiences with Jira, and I think it's only because the person who configured it knew what they were doing. It was also a smaller company so the limited complexity of the project could have also helped.