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

181–190 of 287 posts

Re: I Fucking Hate Jira (2022)

#181

Post by blueskythinking »

circusfly wrote: post #161
blueskythinking wrote: post #103

Earlier quoted context omitted.

Story points represent complexity, not difficulty. We also aim for a certain amount of story points per sprint. After 13 we leave the Fibonacci sequence and just double them. The entire team must vote on story points simultaneously to avoid affecting each other’s opinions, then must discuss the votes until we agree on a number. Stories that have sat too long in the backlog need re-pointing. Voting is now done with po…

At some places, any story higher than 5 gets split, an Epic is created and the 2 (or more) new stories are added to the new epic. I really don't get the online disdain for JIRA unless it's Microsoft employee astroturfers, almost as bad as Jetbrains and Red Hat astroturfers.

Ah, that explains why I keep being asked to split a complex feature into pointless pieces that don’t stand alone. No wonder we need so many team hours in sprint planning, to keep track of them all.

Re: I Fucking Hate Jira (2022)

#182

Post by erik_seaberg »

IshKebab wrote: post #75
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.

Trust me it's distain for the tool. Jira is bad on three fronts: 1. It's too configurable. It's like the company wiki. People come in, set up some random projects, processes, fields, statuses, etc. and then move on. There's rarely someone making it all consistent and sensible. This results in task statuses that can be TODO, BACKLOG, PENDING, WAITING, TO DO, etc. etc. etc. You also end up with waaaay too many fields f…

My favorite is trying to figure out the subtle inflection differences between “won’t do,” “rejected,” “deprecated,” “won’t fix,” “can’t fix,” “cancelled,” “invalid,” “abandoned,” and “declined,” as well as the priority at which we aren’t doing something (um … low?)

Re: I Fucking Hate Jira (2022)

#184

Post by bern4444 »

Eh - I like Jira or rather I don't dislike it.

My team has done a lot of work to lean into the tool IE well defined issues, epics, tickets, t shirt sizing for pointing via 1, 3, 5, etc.

There is lots that can be improved for sure.

With this system, my team, in addition to any one else at the company, is able to click into our JIRA board and get a very high level to a very low level understanding of what we are working on.

This allows for very clear reporting structures and ensures our goals are on track with those of the company's. This also makes outcomes more measureable which is exceptionally helpful for reviews.

At the end of the year or halfway through I can go in and say: I worked on these 4 epics that are part of these two Issues which serve company goals A, B, and C. I completed x% of the tickets for each of these epics, led this entire other epic which was completed on time etc etc.

Where we run into issues is when there is a ticket that has to move between boards. The ideal situation is we just move the ticket from board to board as needed but based on the user they may or may not have permissions and have to open a new ticket linking it to the previous one. Not ideal but that's up to us to resolve to make sure the right people have the right permissions.

We ignore all the analytics IE burn down and friends. Those are useless.

Re: I Fucking Hate Jira (2022)

#185

Post by Tagbert »

NikolaNovak wrote: post #146
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…

Interesting; I think this is a demonstration of how much what seems like a "Tool" is actually "organization", because my current experience is completely opposite: * In MS teams, I can create conversations, group chats, organic meetings, and add people (and include history) as I want and desire. I prefer it for quick discussions with my colleagues and to get a rapid problem solving or critical incident conversation w…

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 can convert a adhoc group into a Channel and decide if it will be private or public. You can click to start a call or to start a zoom with those present in the group or channel. it's pretty seamless, too.

It sounds like the difference is your organization.

Re: I Fucking Hate Jira (2022)

#188

Post by throwawaaarrgh »

The only valid reasons to hate Jira or Confluence are when you work for a company that has no governance structure for them. You do have to use the tools correctly for them to not suck. This is true of all tools.

When you learn how they are supposed to be used, and use them that way, they work really well. Sadly I have only met three people in my entire career who did so. Their job titles were scrum master, release manager, and project manager. They had to learn how to use the tools because that was their job.

And so they did. They could do literally anything we asked them to. They showed us all kinds of amazing things we didn't know we could do. All because they took a few hours of training and read the docs. That's when I learned that my own parroting of "I hate Jira" was just my own ignorance showing, and I grew up a bit. I really like Confluence now; I didn't even realize it was a Wiki before.

Re: I Fucking Hate Jira (2022)

#190

Post by sodapopcan »

noddingham wrote: post #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.

This, yes, but it's also sllllllow. I'm assuming this is due to the high configurability (all those options must be a pain to cache) but that is just a guess. In any event, I moved to a company that used Shortcut (formerly Clubhouse) and it was crazy fast! Like, every action was sub 100ms. While it worked very similarly to how my previous company had configured Jira, I found myself missing some stuff, mostly Jira's backlog. My current company uses Zoho and its "Projects" module is a similar but different pain from Jira. It also suffers from being way too configurable.
Post reply on HN