As others have mentioned, check out: https://linear.app
https://height.app is also quite good
Why Jira Sucks
191–200 of 530 posts
Re: Why Jira Sucks
#192Earlier quoted context omitted.
I'm a developer and I can't remember anything so I love JIRA. I just grab a ticket and have everything I need to work on it.
You are an assembly line robot.
I've been the core dev on an 18 person team, I wrote 80% of the jira tickets and did about 35% of the code. 6 month of coding project to first launch. I used jira to remember. I wrote tickets for missing features, kludge's and bugs to be fixed, etc. I yelled at the managers to prioritize and estimate faster so I would know how on track we were or if we needed major strategy pivots.
Yes I'm an assembly line robot and the plant foreman. Jira and delegation helped me pull off both
Re: Why Jira Sucks
#193Earlier quoted context omitted.
I'm a developer and I can't remember anything so I love JIRA. I just grab a ticket and have everything I need to work on it.
You are an assembly line robot.
Pretty sure that's what the majority of programmers are. I know I am. My identity isn't wrapped up in programming. I build stuff for a company that pays me lots of money and then I go home and do stuff I like.
We need to get rid of this wild west mentality where disorganization is lauded.
Re: Why Jira Sucks
#194To 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…
A git commit is a process document. Developers don’t like JIRA. I’ve already left traces of my process when I pushed the code. Developers love GitHub. A robot will associate my git commit with the ticket and mark the ticket accordingly. As a developer I don’t like repeating my self. A robot should be able to catalog my process documents. If middle management wants to use JIRA it needs to be set up so that a developer never has to write to it. The only JIRA a developer will be happy using is a JIRA they don’t have to work with.
Re: Why Jira Sucks
#195Earlier quoted context omitted.
Native support for Markdown in comments would be a good win. In the Atlassian ecosystem, the markup languages are constrained by the following equation: JIRA Markup != Confluence Markup != Bitbucket Markup
Also even just within JIRA it can be inconsistent - I realised that to make monospaced text you need to use: - backticks when creating a Jira ticket, e.g. `hello` - double curly-braces when editing a Jira ticket, e.g. {{hello}} ... or vice versa. I cannot honestly remember which way round it is. Of the complaints I have about Jira this is probably the least annoying - but it really shows how irritating the product is…
It's vice versa, and this may be a small thing but it's my top example of how little they care about usability or product quality!
Re: Why Jira Sucks
#196The one thing that annoys me is that even after all these years of JIRA they still haven't fixed their shitty WYSIWYG editor. I can't count the number of times I've written something and then end up with random asterisks all over the place because it failed to figure out what is bold or what's in a list or whatever.
Re: Why Jira Sucks
#197To 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…
> And I've also never worked anywhere that had a better option than JIRA.
Agree with most of what you say aside from this bit. I find most similar systems are in the same ballpark in terms of being able to track what I care about.
Mainly:
- Is the ticket ready for me to work on? (Do I have the designs I need to work it?)
- Who is working on a given ticket right now?
- Am I done with a ticket?
- Is the ticket ready for QA?
- Did QA reject the ticket and I need to fix something on the ticket?
Pivotal does these things fairly well. There is also the obligatory pointing system, but the above is the bulk of what I care about. Pivotal also lets me create queries so I can zero in on the work which I'm doing as opposed to the entire project.
Re: Why Jira Sucks
#198Earlier quoted context omitted.
You are an assembly line robot.
How do you prefer to gather the context for something that may have been hashed out months or years ago by different people?
The idea that a task can and should be "hashed out months or years ago by different people" is part of the JIRA mentality. And it is absurd.
Re: Why Jira Sucks
#199There's a hundred small issues with Jira, but there's one huge one: It's slow. Really, really slow. Atlassian seems to make a lot of money, so I guess they're optimising for something that matters to someone , but from my point of view I have a simple process for evaluating tools: 1) Can I use it at all ? 2) How many of the features I want does it have? I'm pretty sure Jira would score great on the second question, b…
A customer I am currently working with has a JIRA instance which literally, looking at the firefox network inspector right now, takes 13.04 seconds before it's done loading. It takes at least 10 seconds before the page will even let me scroll. I can't even comprehend how they have managed to get this poor of performance.
Re: Why Jira Sucks
#200We're getting off our old ticket/wiki project system this coming year as it's being sunsetted. Jira is one of the alternatives we're investigating, because several staff have used it in other jobs. I also used it for a brief time, and I was not in love with it. I often felt like it was arguing with me. There are so many systems out there. Right now we're also evaluating YouTrack from JetBrains and OpenProject.org (wh…
JIRA is just fine. Can't really go bad with it. If you have limited needs, you can try GitHub or GitLab Issues. But for a team which may end up growing, JIRA will work. It has good integration with GitHub/GitLab, and with Smart Commits enabled, most of workflows can be baked into it. It's slow, but judging by this thread, I suspect Atlassian customers are complaining about it too, so hopefully it'll be heard.