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

I Fucking Hate Jira (2022)

ifuckinghatejira.com

Post reply on HN
Print view View original

221–230 of 287 posts

Re: I Fucking Hate Jira (2022)

#221

Post by VonGallifrey »

lmm wrote: post #191
VonGallifrey wrote: post #73

Earlier quoted context omitted.

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…

If one company uses a tool badly that's a bad company. But if most companies use the tool badly that's a bad tool. Jira certainly seems to push people towards having a handful of manager users who are the only ones who can create boards/transitions or adjust which fields are mandatory, and this leads to bad behaviour - if only one VIP can create boards, they'll probably create 20 once and then never create another. "…

Well... for us every team gets a "Project" and the Team Lead is admin for the Project. The TL can then Create Boards, Issue Types, and Workflows. The Team is in control of what their Board and Workflows look like. Not some far away manager and if we do need the company Jira Admin to do something, it just needs a IT Support Ticket and that will be handled.

We set up our Board and Workflow fairly minimal. Which is probably why I don't have any problems with Jira.

> And "transitions are impossible by default and only possible if enabled by the admin" is a uniquely bad Jira-ism that other tools in this space don't have

What do you mean by that? The default Workflow in Jira is that all Issues can transition into any status.

Re: I Fucking Hate Jira (2022)

#222

Post by ClimaxGravely »

vundercind wrote: post #144
ta1243 wrote: post #59

Earlier quoted context omitted.

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…

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…

2) Is that the equivalent of a slack huddle?

Re: I Fucking Hate Jira (2022)

#223

Post by ClimaxGravely »

NikolaNovak wrote: post #202
Tagbert wrote: post #185

Earlier quoted context omitted.

That sounds like you have a very top-down organization and they have setup Slack to mirror that dynamic. Slack by itself does not have those restrictions. Individuals can create Slack Channels (often too many channels). You can setup adhoc groups through DM and can add people to that group . You have the choice when adding people to a chat to block the history or give them full access to the history. At any point you…

Yes. That is the very first sentence in my post :). A lot of our presumed perspective and experience with tools is actually our experience with organizations and policies. Conversely, majority of issues I've read here with Ms Teams, are not part of my own experience - Teams I use is way easier and more flexible and user friendly than the slack I use. Is it the case that more startups used slack vs more enterprises us…

I wonder about that too. I've used both and personally I consider neither vastly superior to the other or even that much different.

Re: I Fucking Hate Jira (2022)

#224

Post by lmm »

VonGallifrey wrote: post #221
lmm wrote: post #191

Earlier quoted context omitted.

If one company uses a tool badly that's a bad company. But if most companies use the tool badly that's a bad tool. Jira certainly seems to push people towards having a handful of manager users who are the only ones who can create boards/transitions or adjust which fields are mandatory, and this leads to bad behaviour - if only one VIP can create boards, they'll probably create 20 once and then never create another. "…

Well... for us every team gets a "Project" and the Team Lead is admin for the Project. The TL can then Create Boards, Issue Types, and Workflows. The Team is in control of what their Board and Workflows look like. Not some far away manager and if we do need the company Jira Admin to do something, it just needs a IT Support Ticket and that will be handled. We set up our Board and Workflow fairly minimal. Which is prob…

> The default Workflow in Jira is that all Issues can transition into any status.

The default workflow in some newer editions has a transition that allows that yes. But custom workflows don't have those transitions unless and until an admin manually adds them. If the person who set up the workflow didn't think of some edge case, you're SOL.

Re: I Fucking Hate Jira (2022)

#225

Post by ClimaxGravely »

morkalork wrote: post #21

Confluence is where documentation goes to die.

I loathe confluence, tried to get a markdown plugin around 2016 and IIRC the charge was 5$ per person at the company per month.

For what it's worth it's a lot better than it was in 2016 but I'm still not a fan.

Re: I Fucking Hate Jira (2022)

#226

Post by ClimaxGravely »

Within the last 2 weeks Jira has begun to do some constant refresh cycle that is killing me (this is on chrome which I've been updating regularly hoping it gets fixed). The worst part is while I'm typing in one field it will seemingly randomly refocus me to a different field and start inputting text there. Only about ~5-10% of the company seems to be affected though so it's not being actively looked at.

Now I just write all my jira stuff in a external text editor and paste it in.

Re: I Fucking Hate Jira (2022)

#227

Post by MichaelZuo »

dakial1 wrote: post #95
DarkNova6 wrote: post #37

Earlier quoted context omitted.

I am thinking the exact same thing. Right now I wish I could use Jira because I‘m using this IBM equivalent tool „CCM“. CCM is so bad it’s nearly dysfunctional. Image Jira but 3 times the necessary clicks (this is not hyperbole). With Jira I can see the good intentions and how they go awry. But CCM is pure madness from top to bottom.

Even IBM is getting rid of IBM (or ex IBM) stuff. They are using outlook now, lots of teams use Jira/Trello/Confluence etc...

They sold their in-house wiki system back in 2019 so they pretty much are forced to.

Re: I Fucking Hate Jira (2022)

#228

Post by schappim »

justinsaccount wrote: post #10
schappim wrote: post #6

Several of the complaints mentioned are over a decade old. For instance, I searched for "I **ing hate JIRA too, the interface is clunky and slow and makes me angry.," and found it was from this comment from Feb 2014 [1]. It is perhaps a bit disingenuous to not to include dates. 1. https://www.reddit.com/r/sysadmin/comments/1z07fi/my_company...

I fucking hate JIRA, the interface is clunky and slow and makes me angry. - Me, 2024.

Haha, love it... I'm so glad that I don't work for an organisation that requires me to use tools that get my blood this boiling!

Re: I Fucking Hate Jira (2022)

#229

Post by submain »

jdmoreira wrote: post #50
submain wrote: post #38

Earlier quoted context omitted.

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…

Your developers must be children then. (Maybe because you treat them like children). The source of truth is their changelog not your Jira tickets

Quite the opposite actually. My developers barely touch their tickets. Most of the updates are done rather informally. They mostly interact with git and I make sure things are tracked.

You’ve used quite strong words there.

Re: I Fucking Hate Jira (2022)

#230

Post by VonGallifrey »

lmm wrote: post #224
VonGallifrey wrote: post #221

Earlier quoted context omitted.

Well... for us every team gets a "Project" and the Team Lead is admin for the Project. The TL can then Create Boards, Issue Types, and Workflows. The Team is in control of what their Board and Workflows look like. Not some far away manager and if we do need the company Jira Admin to do something, it just needs a IT Support Ticket and that will be handled. We set up our Board and Workflow fairly minimal. Which is prob…

> The default Workflow in Jira is that all Issues can transition into any status. The default workflow in some newer editions has a transition that allows that yes. But custom workflows don't have those transitions unless and until an admin manually adds them. If the person who set up the workflow didn't think of some edge case, you're SOL.

Since the person that made the workflow is always the Team Lead we are never "SOL". It is a 2 minute thing to fix a workflow.

Sounds to me like you probably never edited the Jira workflows yourself. If it takes your company more then an hour to change a workflow then that is a decision to artificially limit things.

Also: Custom workflows start with with the "Any" transition on all states and when adding a new status it also has the "Any" transition. If that is different in your workflows then that is a deliberate decision.

Post reply on HN