Live data from Hacker News

I Fucking Hate Jira (2022)

ifuckinghatejira.com

81–90 of 287 posts

Re: I Fucking Hate Jira (2022)

#81
post #38
post #7

Jira tries to solve everyone’s problem. It tries to incorporate everyone’s idea of how and what’s needed to be tracked. I can just say from my own experience that the one that created the workflow and what fields that they absolutely must have to do some sort of follow up, have never worked as a developer or anything near a software project, and yet enforces all this garbage for their illusion of control. And yet the…

I share the sentiment and frustration of having to fill useless boxes. However, as a manager, things go south very quick if you're not tracking what's being changed and by whom. You won't know what's included in your release, nor if it was tested properly. You won't know who to reach for fixes after testing or even what to tell clients when they ask if a feature/fix was shipped. I hate overly complicated processes, b…

>tracking what's being changed and by whom

git

>You won't know what's included in your release

release notes

>nor if it was tested properly.

CI

Re: I Fucking Hate Jira (2022)

#82
Jira's much more a toolbox than a tool.

If you have someone with the knowledge to use what's in the toolbox and the scope to build flows that support how work is done in your org, you'll love Jira, because it'll work far better for you than anything else could.

If you don't have someone like that, or if you're small enough not to want or need that yet, then you'll fucking hate Jira.

Re: I Fucking Hate Jira (2022)

#83
post #8

I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.

I've worked in both large and small orgs with Jira. Hate it just as much in small orgs. Maybe more even.

Re: I Fucking Hate Jira (2022)

#84

Agreed. Other than Linear, are there any task trackers that people enjoy using?

Phabricator (or Phorge) is pretty great on that front. I think the basic Github and Gitlab systems are also all you really need. I mean Gitlab uses it and they have 60k issues and 2000 employees.

I think the key is to have good search, which Jira does not remotely have.

Re: I Fucking Hate Jira (2022)

#85
I got two slides in before I disagreed with everything. JIRA does not emphasize how over why. It literally just has a text box for a description. What you write is up to you. JIRA does not discourage in-person conversation. JIRA is there to document conversations and it's incredibly good at it. Any PM tool that doesn't allow threaded comments is dead to me.

I've never spent more than like an hour training anyone on JIRA and have used it successfully for many, many years.

Re: I Fucking Hate Jira (2022)

#86
post #77
post #8

I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.

I've wondered the same thing about Microsoft Teams. Is Teams as horrible as people say, or do they just hate it because it's what they happen to use for video meetings at work? Conversely, I don't hear much hate for zoom.

I can’t get a modal popup when someone messages me directly on teams. I have to check the list of chats for if someone has messaged me.

That’s stupid and a flaw in teams. It’s a bad messaging app. It’s pretty good with meetings though.

Re: I Fucking Hate Jira (2022)

#87
post #24

Earlier quoted context omitted.

i wonder how common this is, and why havent you heard of it, specially that you know about this site hacker news this is almost on the same level as someone saying he never heard of subversion

Not sure why. But feel free to recommend a better tool, since I will need something like this soon. How about this? https://www.openproject.org/

As a developer, OpenProject is fine.

Search is pretty good, so I assume the reporting is okay, but I've never tried it.

We used to get occasional slowdowns, but someone threw more HW at it, and speed is good now.

I've never used Jira, so I can't compare directly.

Re: I Fucking Hate Jira (2022)

#88
post #38
post #7

Jira tries to solve everyone’s problem. It tries to incorporate everyone’s idea of how and what’s needed to be tracked. I can just say from my own experience that the one that created the workflow and what fields that they absolutely must have to do some sort of follow up, have never worked as a developer or anything near a software project, and yet enforces all this garbage for their illusion of control. And yet the…

I share the sentiment and frustration of having to fill useless boxes. However, as a manager, things go south very quick if you're not tracking what's being changed and by whom. You won't know what's included in your release, nor if it was tested properly. You won't know who to reach for fixes after testing or even what to tell clients when they ask if a feature/fix was shipped. I hate overly complicated processes, b…

There are already 4 replies telling you that you're trying to reinvent source control, and that's still not enough.

Re: I Fucking Hate Jira (2022)

#89

I wrote “Jira Is a Code Smell”: https://honeypot.net/post/jira-is-a-code-smell/ Short version: Jira, in a vacuum, is neither great nor awful. It just is. But it has a complication that makes managers I want to work for dislike it, while strongly appealing to managers I don’t want to work for. That’s not universally true, I’m sure. However, it’s been my experience.

> But it has a complication that makes managers I want to work for dislike it, while strongly appealing to managers I don’t want to work for.

I think that could also be described as Jira gives people who don't really have anything to do, something to do, but for those who are blessed with an abundance of work, Jira can be unnecessary overhead.

Re: I Fucking Hate Jira (2022)

#90
post #8

I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.

My team does a lightweight agile process, we don't hate it. If we used a better tool, we'd love it. We have Jira, and I don't have the energy to change it, nor do I want the responsibility to decide or suggest what other tool that should be. I've always used Jira, I have no suggestions ready. I'm sure it's easy to pick a simple tracker, like GitHub Issues, but I would not know if it'd suffice all our needs and if it…

- Monday.com

- Airtable

- A giant board on Miro.com with a bunch of notes in frames

Of course the scaling needs are different whether it’s for just a single team or if the data needs to be aggregated into some KPI. In my experience it’s better to keep KPI publishing separate from task tracking, though

Post reply on HN