Live data from Hacker News

I Fucking Hate Jira (2022)

ifuckinghatejira.com

171–180 of 287 posts

Re: I Fucking Hate Jira (2022)

#171
post #167

Earlier quoted context omitted.

Teams would be fine with two things: 1) Let a Team channel be a normal-ass chat instead of some weird forum-in-a-chat-interface. Shit gets lost. Creating a new post feels very formal and high friction, because it’ll push everything else out of view (another, minor problem: teams’ padding and whitespace is way out of control). Make it configurable! That’s ok. The weird chat-as-forum thing is fine for a very low-traffi…

There is probably some feature request somewhere in Microsoft weird tech channel with thousands of comments and upvotes and some MS person appearing every three years to let us know they "are looking into it".

There were a couple years-old ones on public feature request sites last I checked. They’re ignoring them.

It’s frustrating because Teams can already do normal chat rooms, and can already schedule meetings. Just not in the most-useful places to have those two features. It’s not brand-new feature development from scratch.

Re: I Fucking Hate Jira (2022)

#172
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.

JIRA is a silly proprietary system, there's just no clearly stated case case for using it when we've got open alternatives like Phorge (née Phabricator) that also see wide-ranging use.

Re: I Fucking Hate Jira (2022)

#173
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.

At my last large tech company we moved from Phabricator to JIRA. It was a global downgrade for actual users through and through. Engineering hated it, usage of ticket tracking went down a lot because nobody wanted to interact with that crappy tool. A good chunk of team's tasks just went into more informal google docs, sheets & slack channel bots as a result and the teams responsible for managing the tool had a hard time getting real adoption.

We were forced to get off of Phabricator because it was abandoned, but JIRA was still a downgrade in every way. Linear will eat JIRAs lunch and in a decade, it's going to go the way of HipChat as the thing that everyone used but nobody talks about.

Re: I Fucking Hate Jira (2022)

#174
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.

When I clicked on the site the very first opinion called Jira shit because they had 20 different boards for the same thing, 2000 tickets in the backlog and 20 different mandatory fields for each ticket. Which is absolutely not the fault of Jira. Jira does not make you create 20 boards and per default a Title is all you need to create a Ticket. By the complaints own wording they had 2000 tickets because management ref…

I'm not going to "stan" for JIRA, but I've developed software before Jira with Bugzilla and other smorgasborgs of tools.

JIRA was a dramatic improvement at one point, however, it is bought and sold to managers, so it is unsurprising it eventually converges to managerial overengineering.

Re: I Fucking Hate Jira (2022)

#175
post #127

The problem with JIRA and its ilk is that they try to do bug tracking, planning, and historical data all in the same tool, when those are really separate problems. Have a bug? JIRA makes perfect sense, you have a ticket with comments, it keeps track of how long it's been around, it can automatically move the bug through a process, etc. All these tools started out as "bug trackers" after all. Trying to plan future wor…

JIRA includes integration for Github Enterprise. If a commit message or branch references an issue number, it will automatically be included in that JIRA issue.

Re: I Fucking Hate Jira (2022)

#176
post #59
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…

“Jira is brilliant”

I've never read that sentence before!

My feeling is... developers hate Jira, managers love Jira. And that is expected. The tendency is for things loved by managers to be hated by developers, such as meetings, metrics, etc.

An example of a very misused metric: In one of my jobs, managers started using Scrum Poker results as a productivity measure. “My team scored 100 points in the last sprint.” Imagine the chaos this generated. Quickly teams began to hate the Scrum poker.

Jira is probably just a scapegoat in corporate theater, something needs to be to blame. Jira is a good culprit.

Re: I Fucking Hate Jira (2022)

#177

Confluence is where documentation goes to die.

I much prefer Confluence to something like myriad Word and Excel sheets of uncanny versions floating around mostly unknown Sharepoint locations.

At least you can search more or less properly in network folders.

At my old work I usually left a search going from the root network folder over the weekend, scanning for some keywords, when I needed a doc none knew where it was or if it existed at all.

There was a parallel documentation system from IBM that didn't work, where the canonical docs should be. But you more or less had to know the document ID to query it. So most documents were also in the network folders spread out between hundred project folders and meeting folders.

Re: I Fucking Hate Jira (2022)

#179
post #70

Earlier quoted context omitted.

It's the worst documentation tool, except all the others. Seriously though, what is better?

I’ve been pretty happy with Slab. Straightforward shared wiki with a good editor, governance, and integrations. https://slab.com/ I tried using README files in the repo but there’s far too much friction to get most folks to bother. Google Docs tend to disappear content due to a lack of structure.

> I tried using README files in the repo but there’s far too much friction

I have confluence links in my Readme, which seems to be a pretty good balance, since it's physically impossible for people to use a search bar in a wiki.

Re: I Fucking Hate Jira (2022)

#180
Jira needs an admin to help manage the configuration. It's like a Swiss army knife and the reason many teams hate it is because they don't have an admin helping them get what they need out of it and keep the rest of the tool out of the way. The flexibility is both a blessing and curse. If you don't like Jira it's likely your configuration is shit, or your process is shit, or both.
Post reply on HN