3 ms·

My fave thing about Jira is how between the tool & it's plugins, you can roll up all sorts of views for management reporting purposes. Despite this, exactly ze

My fave thing about Jira is how between the tool & it's plugins, you can roll up all sorts of views for management reporting purposes. Despite this, exactly zero shops I have worked do management believe their managers will understand those views. Therefore at a weekly/monthly/quarterly cadence, "someone" (dev leads) have to spend hours hand updating some horrific excel view of project statuses for big management to understand.

kdinn 4y ago
> Therefore at a weekly/monthly/quarterly cadence, "someone" (dev leads) have to spend hours hand updating some horrific excel view of project statuses for big management to understand. You're spot on about that. I've been the "someone" dev lead doing this so often I decided that someone should build a system that does this. You can see my progress so far at fixed.pm
steveBK123 4y ago
Also this is "agile"
ratww 4y ago
All I really see managers using is the burnup or burndown chart. They seem to choose between up/down based on their current mood. But it doesn't matter which one they choose, it always seem to bring everyone's mood down anyway. And yet when you ask if we can change from JIRA to something else they say "but my reporting".
BoorishBears 4y ago
Absolute worse part of Jira. Twice now I've worked at places that used Jira, and all it takes is one corner of the company to leverage it for some random oddball purpose to make it painfully slow. One place started using it for managing thousands of assets, and eventually they were paying contractors tens of thousands to optimize their JIRA instance and untangle the mess. Same thing is happening at my current company, where even in the last few months it's gotten painfully slower.
- ratww 4y ago
  Wow. I had erased this from my memory, but: in a company I worked previously, every single string that had to be localised had to go into a JIRA task, after going into an internal localisation tool. Eventually they needed a separate JIRA instance with different logins because there were hundreds of new "strings" being created daily, some of those coming from user content.

kdinn 4y ago

> Therefore at a weekly/monthly/quarterly cadence, "someone" (dev leads) have to spend hours hand updating some horrific excel view of project statuses for big management to understand. You're spot on about that. I've been the "someone" dev lead doing this so often I decided that someone should build a system that does this. You can see my progress so far at fixed.pm

steveBK123 4y ago

Also this is "agile"

ratww 4y ago

All I really see managers using is the burnup or burndown chart. They seem to choose between up/down based on their current mood. But it doesn't matter which one they choose, it always seem to bring everyone's mood down anyway. And yet when you ask if we can change from JIRA to something else they say "but my reporting".

BoorishBears 4y ago

Absolute worse part of Jira. Twice now I've worked at places that used Jira, and all it takes is one corner of the company to leverage it for some random oddball purpose to make it painfully slow. One place started using it for managing thousands of assets, and eventually they were paying contractors tens of thousands to optimize their JIRA instance and untangle the mess. Same thing is happening at my current company, where even in the last few months it's gotten painfully slower.

ratww 4y ago
Wow. I had erased this from my memory, but: in a company I worked previously, every single string that had to be localised had to go into a JIRA task, after going into an internal localisation tool. Eventually they needed a separate JIRA instance with different logins because there were hundreds of new "strings" being created daily, some of those coming from user content.