undefined | Better HN

0 pointsstiray5y ago0 comments

> is just how easy it is to create bureaucracy-intense workflows in JIRA and make management believe these are absolutely necessary

Omg, finally someone has said it, I thought I was weird. This is the imperative problem with JIRA, it is not made to help the developers but to satisfy management which is buying the software. +1 for this comment. I have seen its usage in 7 companies and in each and every case instead of simplifying developers workflow it was complicating it due to management wanting to have their data which, at the end, didnt bring anything for the product but were just enabler to make their cute graphs that enabled them to not be involved into development cycle (as they should be) but rather bring out statistics "out of their shoe - JIRA".

And this is also my only (ok, except the slowness which should be understandable for any web browser js application) comment over the JIRA, I dont care what the tool is, how much time it takes (at the end, I am not paying for it), but how much it diverges from the tool that SHOULD help the development while in its essence it mostly helps the management to track their data.

0 comments

1 comments · 1 top-level

BlargMcLarg5y ago

Pretty much. We can divert a little to support customers reporting issues, though I don't feel JIRA is much friendlier here compared to GitLab once you get the hang of both. The only one I see benefiting from this monstrosity is management and upper layers, and they indirectly pay for this through lower morale and retention rates. If you really need the graphs that badly, you might as well spend a few hundred man hours to write a script that imports data, run some data science logic and draw them. And maybe put all that info.

j / k navigate · click thread line to collapse