In my experience, Jira is the dog that begins to resemble its owner. If you are working in a toxic, dysfunctional organization, Jira will reflect that: - Giant forms with dozens upon dozens of nonsensical fields (preferably with abbreviations as names, like "IFE App.") half of which are required so you just stuff random words in them to make it shut up - Thousands of tickets that would probably take 30+ software devs…
> - Thousands of tickets that would probably take 30+ software devs 100+ years to implement I feel like the company I'm working for has a reasonable attitude towards Jira, and they recently just batch closed all tickets that were older than some date in many projects. So you'd have to actively re-open tickets you had created to keep them alive, if needed. Great decision IMO. It's an interesting exercise to be forced…
There could be alternatives e.g., label such task as "fun" and hide them all the views by default, then allow developers to spent say 10% on any of "fun" task of their choosing (no expectations).
It may help with burn-out for some devs and the issues that are worth fixing according to at least by some devs are getting closed eventually.