Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Jira Sucks

whyjirasucks.com

Post reply on HN
Print view View original

351–360 of 530 posts

Re: Why Jira Sucks

#351

Post by Kwpolska »

pigeonbacon wrote: post #233
Lazare wrote: post #119

There'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…

Do you know that this post is actually breaking the JIRA ToS? Seriously, it's in their ToS that you can't complain about how slow JIRA is... > Except as otherwise expressly permitted in these Terms, you will not...(i) publicly disseminate information regarding the performance of the Cloud Products https://www.atlassian.com/legal/cloud-terms-of-service JIRA sucks

The OP never stated they’re using it on Atlassian’s cloud, and Jira is available for on-premises deployments too, where those terms don’t apply.

Re: Why Jira Sucks

#352

Post by pm90 »

turbinerneiter wrote: post #187
SideburnsOfDoom wrote: post #172

Earlier quoted context omitted.

> Jira makes it easy to track what's actually going on. No it does not, and I said that above more than once. it makes it easy to track what's in JIRA, that's all. To the extent that it's accurate, it constrains what's "actually going on".

Exactly. What's going on is commits and merges. They live in GitLab. There is also tickets in GitLab, which all developers are happy to use. There is a wiki as well, which, gosh, is just markdown in another repo! Markdown you can build beautiful PDFs from! And websites! But nope, we need JIRA and confluence, because for some reason GitLab isn't good enough. Now the tickets are separate from the actual work, there is…

The constraint for the org I work in is that GitHub has a per user license fee that makes it difficult to justify getting a license for everyone in the org since we have a lot of non developer staff. But everyone has access to confluence/JIRA. Does Gitlab also have similar license restrictions?

Re: Why Jira Sucks

#353

Post by rightbyte »

specialist wrote: post #315
ccwilson10 wrote: post #303

Earlier quoted context omitted.

Welp... fun fact, every team (even the non-tech teams) uses Jira so I'll happily send over my venmo account :p

You can split the prize money with u/p2tp2. I legitimacy want to see this. Hire some film students, have them embed with some teams for some sprints, post the footage. If Atlassian really does walk the talk, why aren't you already bragging about it? I just peeked at Atlassian's YouTube stuff. Nicely produced. So that's something. I'm not even going to move the goal posts, or play No True Scotsman. Show how any team a…

> I legitimacy want to see this.

I wish I was sarcastic when I said I agree. Seeing a working 30 min sprint planning. Instant hit.

Re: Why Jira Sucks

#355

Post by ctrager »

When I read the list of reasons "Why Jira Sucks" what came to mine was the Charlie Kaufman movie "Synecdoche, New York". In that movie, a playwright keeps expanding the scope of a play to more and more encompass the scope of reality itself. Likewise, some of the points (1, 2, 3, 5...) in the writer of "Why Jira Sucks" wants Jira to be bigger, to encompass the variety of ways work can flow.

Re: Why Jira Sucks

#356

Post by smcl »

julenx wrote: post #114
smcl wrote: post #95

Earlier quoted context omitted.

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…

I haven't used JIRA recently, but as far as I remember the difference existed because they were rolling out a "new" editor, which was active when editing tickets, but wasn't available when creating new ones. I remember this caused me some data corruption when editing a comment created with the old version of the editor using the new editor. It was a mess.

This honestly would not surprise me. I’m kinda glad there’s an explanation, but I’m also annoyed it’s a stupid one

Re: Why Jira Sucks

#357

Post by smcl »

nicwolff wrote: post #195
smcl wrote: post #95

Earlier quoted context omitted.

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!

One hundred percent - it’s such a little thing, but as a developer it says a lot about the code beneath the product

Re: Why Jira Sucks

#358

Post by [deleted] »

SideburnsOfDoom wrote: post #84

To 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…

[deleted]

Re: Why Jira Sucks

#359

Post by jvvlimme »

ypeterholmes wrote: post #349
debaserab2 wrote: post #316

Earlier quoted context omitted.

> I feel that Jira's configurability makes it like desktop Linux 20 years ago. Everybody swears it's rock-solid, beautiful, and easy to configure. Then when you ask anyone to have a look at their specific setup, they'll cover the screen with their bodies and panic, "ah no, I kind of messed everything up recently, haha, but you can't really blame the software for that, can you? Everyone else's installation is super cl…

Redmine is great.

No, it’s not. From a Product Owner point of view, it’s a piece of shit. Hard to set priorities, hard to follow progress. I’ll take jira any day.

Re: Why Jira Sucks

#360

Post by adrr »

tootie wrote: post #153
SideburnsOfDoom wrote: post #84

To 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…

I worked at an org where you couldn’t do anything without and being assigned a Jira ticket. Want to refactor some code so the feature your working on is maintainable, nope you need an assigned Jira ticket. The fact that work units are called tickets and Jira was built originally for desktop support is the foundation of the problem. Don’t think, just code attitude.

Anything is better than Jira including post it notes on a wall.

Post reply on HN