Confluence is where documentation goes to die.
It's the worst documentation tool, except all the others.
Seriously though, what is better?
I Fucking Hate Jira (2022)
41–50 of 287 posts
Re: I Fucking Hate Jira (2022)
#42When it comes to JIRA, I agree, but I find Conflunce to be pretty good tool. Unfortunately, most of the people using it are not very good at writing documents or organizing knowledge in general :)
Re: I Fucking Hate Jira (2022)
#43The thing I fucking hate about jira is that it’s a gateway drug for confluence.
Jira doesn’t actually bother me. Confluence is a tool of satan.
Re: I Fucking Hate Jira (2022)
#44I 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 + 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!"
Re: I Fucking Hate Jira (2022)
#45I 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.
The biggest company I've ever worked in was 120 people, and I hated using Jira. I also hated Jira at the ~100 person company I used to work for, and the 7 person company I worked for a few years ago. Jira has a lot of problems. I've yet to find the one, true, perfect work management system, but of the half dozen I've tried, Jira is the one I like the least.
Re: I Fucking Hate Jira (2022)
#46Jira 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…
[deleted]
Re: I Fucking Hate Jira (2022)
#47I 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 very crud-like unless you add plugins to make it a bit better. (Unless things have changed since I last used it?) That means lots of unnecessary clicking around and waiting for slow page loads when you just want to achieve something simple.
That compounds any corporate-inflicted issues.
Re: I Fucking Hate Jira (2022)
#48Jira 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…
The problem is when your instance has too many masters - all fields are global, then their visibility is controlled at the project level. In a big company with one instance, holy sh!t. There are so many duplicated fields, unused fields. When you go to the bulk change option, it shows you all of these and it goes for days.
It works well if you keep it under control, but word to the wise to any company. Create a governance board that's not afraid to tell a VP to fuck off with their requests for yet another ill-conceived field.
That's from the user / web viewpoint.
Don't get me started on their API. v2, v3 changes - the stuff you can't filter out that bloat responses, etc....
But otherwise, if well controlled, it is good. Or at least one of the least bad systems.
Re: I Fucking Hate Jira (2022)
#49I 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 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.
Gods, anything thats interactive and IBM related is generally annoying and not user friendly.
Re: I Fucking Hate Jira (2022)
#50Jira 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…
Your developers must be children then. (Maybe because you treat them like children).
The source of truth is their changelog not your Jira tickets