Maybe the old, discontinued on-premise version. The cloud version of JIRA is a huge step back.

With that said, Teams is not a good product either.

I beg to differ.

I've not had a real issue with teams since the early 'new teams' release. Nor have I had issues prior.

Using Jira is actually something I dread every day.
Knowing I have to go through the list of tasks and projects, where each click means another few seconds of staring blankly at the screen as it loads.

In an age where I'm used to every interaction having a near instant reaction, using Jira feels like peeling potatoes with a butter knife.

Yes, like most normal people do.

There's a lot of discussion when you're a software dev about the best way to do things, and a lot more is spent on this debate than on actually writing code. One could wonder if there is so much discussion because there are so many good ideas that it's difficult to choose the one that is optimal for the situation.

But then you read one of these posts on lemmy and you are reminded that someone with internet access and thumbs could spare the short time they have to take a shit to egregiously misunderstand a simple fucking slogan, smugly post about their shit take on the internet, and then return to their job where they will then spend hours misunderstanding the simplest of fucking concepts, slowing down everyone else along with them.

I can type out the entire 10 word long name of my sprint into the searchbar, and it Jira will pull up 22 pages of things that are not even CLOSE to what I searched. It's a nightmare to try and find my current sprint among the 65 other team's sprints every month.

Right, the entire issue is that it basically acts as a massive layer of insulation between reality and bad management. The whole thing is like a fucking paradox - any time you make a change to workflows or procedures there's this stupid period where you need to "wait for buy in" where it doesn't matter how outwardly idiotic the change is, you can't actually call it obviously fucking stupid for like several weeks, or you are seen as being contrarian, or causing trouble. And the real bullshit is that the "better" the tools are, the more this effect is amplified. So as an engineer, I have paradoxically come to appreciate bad management tools simply because when someone does something stupid with them, I can call it out more easily.

I'd suggest that 95% of Jira complaints are actually about corporate culture which is felt most keenly through asshole PMs trying to micromanage you through a ticketing system. It's mostly a fine piece of software - if you have a certified wizard to configure it it can be great... if you have a dummy it's going to be barely usable - but you can say the same thing about github issue tracking.

The unfortunate thing is that the teams most likely to use Jira are also the teams I most likely never want to work on.

That's the company's fault for using all the features

Because having more ticked boxes than the competition sells. Doesn't matter if it's of any relevance.

No defect
Will not fix

I use both Redmine and Jira at work. I don't know if we're using an older version but Redmine feels like something from 2001. Even the API for it is unpleasant.

That's actually reassuring to hear. Aside from Chilli, it's the only program I've ever used (12 years going). I've got teamates pushing for changes but jira comes at a high cost. Redmine may look old and I hate that it's written on ruby, but it's free and with some plugins it's been able to suite our needs well.