111–120 of 539 posts
OK, so what don't I like about Jira? 1. It's extremely slow. 2. It's difficult to predict the effect of making any kind of change. 3. The permissions system is so convoluted, I can be the admin of a board, and yet not have permission to see a ticket on it. 4. It relegates the conversation to a second-class UI element, when this is the most important part of any project management system. 5. Trying to operate on a bun…
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…
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…
I think the core problem with Jira is organizations trying to use it to solve complex organization-wide problems. It is an enormous time sink, and using Jira to rule the workdays of employees is the problem.
Anything much more complicated than a checklist is wrong. Jira is an attractor for middle management growth that gives people who don't need to be doing anything something to do, and adding complexity gives more opportunities for more people to not do very much and generally get in the way of execution. It is also a way to give people who aren't very necessary or very good at understanding the big picture something that they can do to do.
Take away Jira and tools that you can order other people to use and you end up with middle management that literally doesn't know what to do because they couldn't organize or ease productivity to save their lives. Jira becomes the thing being managed instead of whatever is actually to be done.
That said, it's certainly not the Right Answer for everyone. But unilaterally hating on it is just kinda childish.
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…
Yeah I've been defended Jira here in the past, too. My opinion is that Jira reflects the organisation that manages it. It's basically a whole lot of customizable UI and permissions hanging off a user-defined state machine. You can set it up so that individual teams can fully administer their own projects, or you can go all the way in the other direction and have centralized, locked-down management where you beg some…
Jira is organization poison, not just a reflection of what an organization is.
If your team has an append-only doctrine to information, like most tech debt mills in the industry have, JIRA will become an extension of that ever increasing pile of unmaintained, disgusting, revolting monolith of excrement that captures every activity in software development.
Nothing can be done about the gigantic monolith of soul crushing chaos therefore we need to embrace it, at the expense of our sanity. Nothing can be done about the hopeless hoarding of irrelevant, duplicate tickets that distract people from work.
JIRA makes it very easy to create new tickets, and much harder to close them. So naturally it becomes a virtual sewer. JIRA is about being able to present a large amount of information to easily impressionable people so that so some people can justify their job.
Ok, it's slow, and navigation sucks, and lots of other things. Workflows are easy to get out of hand, but as long as you keep your workflows lean/tame/flexible, it's mostly "good enough". I suspect a sizable portion of the "Jira sucks" crowd are under the thumb of a maniacal administrator creating intense workflows. That said, which competitor has a visual workflow editor, to which I can add custom statuses/transitio…