The grizzled old guys who say that something "doesn't suck" and mean it as high praise aren't just understated cynics; if anything, they're getting swept up in a wave of irrational exuberance.
Edit: Also, there are never enough conference rooms.
Kudos to the sucky stacks that managed to stick around.
It is very hard to break this cycle, but not impossible.
It's becomes like a weird intimidation thing where people don't want to argue back because non-technical managers might think you're just slow at development or don't know what you're doing.
Every project you’re assigned takes you 3 days instead of the slotted 3 weeks and you start getting board out of your mind.
Eventually, you start making silly and fun side projects to alleviate the boredom. Eventually your silly side projec turns into a real product, and maybe you have a customer or two.
Maybe you quit your job to jump right into it. Maybe it succeeds or fails.
The moral of the story: a boring job is the worst but can also be the best.
(It's of course possible to get a job that doesn't have this problem!)
Creating a government website as a contractor, allowing folks to communicate across great distances, programming accounting software for a hospital, building test hardware for a racecar... none of these will save the world, but there is plenty of meaning in each, depending on the person.
When configured & used properly, it's a lovely tool. When interviewing with companies, them using JIRA is a huge plus for me personally and I would definitely rank them higher than those using something else.
My issue is that JIRA takes a long time to set up in an optimal way. I've worked at places with great JIRA setups, but burnt-out PM's that would spend ages setting their sprints up. The time either came from working late, or neglecting other duties to get stuff done for the devs, which isn't ideal for a project that needs management.
The secondary problem is when you work with someone that really knows JIRA, it becomes the tool for everything. They've invested a lot of knowledge into the platform, so why wouldn't they push it for everything? It's no different to a developer gaining a ton of WordPress knowledge and deciding that WP can be a data store for every software product.
Jira is like C++ or representative democracy or capitalism: compared to your internal mental model of things, it’s a needlessly complicated and shitty system, but try to find an alternative that sustainably works for as many different use cases before writing it off.
(Also, much like these things, Jira takes a lot of heat for things that are just part of the human condition but only seem that way because it’s a mechanism for addressing facts about the world that are inherently annoying to us, especially the fact that a lot of people want dumb shit that you may not personally agree with.)
For example if I remember it has no issue numbers like JIRA making it hard to reference tasks succinctly.
That said, at this point just use the bug tracker that is built-in to your git hosting solution.
The tech is always behind, what should take 1 minutes will take two days.