I Fucking Hate Jira (2022) • Hacker News Board

Re: I Fucking Hate Jira (2022)

#51

Post by stillbourne » Wed, Feb 14, 2024, 9:19 PM UTC

Jira is one of those tools where infinite configurability leads to infinite complexity.

Re: I Fucking Hate Jira (2022)

#52

Post by annoyingnoob » Wed, Feb 14, 2024, 9:20 PM UTC

We are going to need a story for that. Be sure to set a good estimate of your effort in the form of story points. Use the Fibonacci sequence to pick the difficulty level for your story points. Your manager will then arrange your stories in priority order, Stories must be worked in priority order. At review time the number of stories and the number of points per story counts. Hurry up now.

Re: I Fucking Hate Jira (2022)

#53

Post by toomuchtodo » Wed, Feb 14, 2024, 9:21 PM UTC

ch4s3 wrote: post #34

itronitron wrote: post #22

Earlier quoted context omitted.

Jira + Scrum is a soul crushing nightmare, Jira + Kanban is fine.

Until someone comes along and tries to put some scrum into your kanban.

Ahh, someone woke up and chose violence today.

Re: I Fucking Hate Jira (2022)

#54

Post by breather » Wed, Feb 14, 2024, 9:22 PM UTC

teeray wrote: post #44

itronitron wrote: post #22

Earlier quoted context omitted.

Jira + Scrum is a soul crushing nightmare, Jira + Kanban is fine.

"but once we can get our estimates right, then think of all that we can do with these burndown charts!"

Is there a context where time estimation is not employed, even implicitly?

Re: I Fucking Hate Jira (2022)

#55

Post by stickfigure » Wed, Feb 14, 2024, 9:22 PM UTC

Octoth0rpe wrote: post #9

peter_l_downs wrote: post #2

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

I liked pivotal tracker ( https://www.pivotaltracker.com ) quite a bit when I used it at my last job, but that was 7ish years ago. Presumably it hasn't gotten worse. At the time I strongly suspected that it wouldn't scale past 30ish devs. That's more than enough for many people though, and that's assuming no improvements. I particularly liked that there are very nice cli tools for it: https://www.pivotaltracker.com/i…

Can confirm that Pivotal Tracker has gotten better since then, not worse. But it's strongly opinionated and if you aren't using something very much like the Pivotal process, it might not work for you. Personally I love it.

FYI a dozen people would be a huge team at Pivotal. 30 folks working in a single backlog is unheard of. But I hear Pivotal became a different place after Rob left, so I don't know what it's like now.

Re: I Fucking Hate Jira (2022)

#56

Post by glxxyz » Wed, Feb 14, 2024, 9:23 PM UTC

wcoenen wrote: post #17

There is much worse out there. We were forced to use Rally[1] for a few years, and I'm absolutely thrilled that we're going back to Jira. [1] https://www.broadcom.com/products/software/value-stream-mana...

I was at a company where we were forced to migrate from a simple lightweight internal tool to Rally, against my advice. It was much worse, and we migrated back within a year. Waste of everyone's time, and our issues got completely mangled and all the formatting looked like total garbage.

Re: I Fucking Hate Jira (2022)

#57

Post by hkchad » Wed, Feb 14, 2024, 9:24 PM UTC

The issue w/ jira is usually the people running it. Jira will let you customize just about every aspect of it, this typically leads to a garbage experience.

Re: I Fucking Hate Jira (2022)

#58

Post by wwilim » Wed, Feb 14, 2024, 9:24 PM UTC

fuzzy2 wrote: post #25

morkalork wrote: post #21

Confluence is where documentation goes to die.

Where would it need to be not to die? Also, what kind of documentation? Technical? Or business?

In the repo with the code, linked to from a sensible wiki that serves only as an index

Re: I Fucking Hate Jira (2022)

#59

Post by ta1243 » Wed, Feb 14, 2024, 9:24 PM UTC

bschne wrote: 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 work in a mid-to-large org. The more agile part use tools like jira and slack. The older part (established in the 1920s) use Remedy and Teams.

Jira is brilliant. It is team-led. Different teams have different approaches, some love all the features like components, versions, issue types, assignee, kanban boards, scrumms, reports etc etc. Others like my team use it with subject/description/comments. You make the tool fit what the team needs.

Same with slack, you can create and destroy channels around your team -- anyone can create any channel at any point it makes sense -- problem at 3AM, spin up a channel to discuss it, job done. You can integrate and add plugins nice and easy.

Remedy and Teams are led top down. They're designed to be organised, not organic. They're not built for the teams doing the work, but for the people wanting reporting. It's more about monthly KPIs than actually improving performance.

I have no doubt you can use Jira in a "KPI led" way. I do doubt you can use Remedy in a responsible way, but even if you can, it relies on the culture of those selling the tools.

Sadly I fear jira and slack will be next -- they already took Zoom and gave us teams instead, after all we "already pay for teams with office" (which aside from cloud-based email, I, and my teammates, never use).

Never has an anti-trust move been so obvious or damaging.

Re: I Fucking Hate Jira (2022)

#60

Post by kstrauser » Wed, Feb 14, 2024, 9:25 PM UTC

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.