Please clarify why Jira software is so unpopular among devs.🤔

I like Jira personally

it's a piece of abomination designed to make dev lives full of agony and pain

It's just so clunky to use

It's designed as a product to sell. not a product to be used.

When I used Jira at my first job it was nice and simple.

Creating tickets didn't get in the way. Now I have to spend half a day on my sprint just to create tickets in Jira

It's slow and too many options and everyone is confused

The workflow is not intuitive

But mainly it's because it's slow. It just lags. Pages don't load well. Needs to be slimmer.

Also I can't organize anything in it. When I used it I kept using tabs to keep track of my tickets instead of browsing to them because it was ridiculous trying to figure out where the project I was supposed to be working on was

Also it's slow. Did I mention slow. It's just slow, honestly.

And who wants a billion features? Why wasn't there a website for the devs and a website for the managers, and they just simply shared the same backend?

I'd also suggest customization options maybe. Honestly it's to the level of complexity it is its own IDE

Also it's slow. Plainly it's just slow. I rather use any other ticketing software. I don't know why that company used jira because GitHub was fine (which is what they used prior) and _not slow_

@jestdotty I was gonna list being slow as a reason too.

But tbf. I think it may be because they have so many customers. Maybe their on prem offering would be much faster

@jestdotty it IS laggy. It ain’t bad overall I kinda like it in spite of other issues. Plus it has its own SQL query language called JQL-that’s the most baffling thing at least to me lol. Gotta be one of the most useless features I’ve seen in a ticket tracker.

I remember using bugzilla back in the day. It was ugly but it WORKED. No more overengineered garbage adding shit like JQL 😅😅. *QL is for bulldozing through billions of rows in db tables, not for a few damn tickets 😅😂

I miss FogBugz

It’s alright but it’s too confusing for them simple-minded managers

- It's intended to be easy to use for EVERYONE and be used for ANY methodology, making its workflow cumbersome
- It's developed by Atlassian, who don't give a fuck about important/useful feature requests or making your life easier. Force you to use paid plugins
- Any somewhat advanced Jira JQL/automation is only possible through paid plugins
- The jira admins I've experienced are either completely unaware of the wishes of the actual daily users or simply do not understand how you can get the most out of it
- It gives developers yet another application we need to use while all major CI/CD providers provide the same required functionalities in a simpler workflow with way better integration

Look, I like the idea of Jira, but admins rarely allow you to use any automation and/or plugins to actually get something valuable out of it and instead try to make the ticket flow inefficient. And I want to pair my goddamn tickets to git branches which nobody ever implements in the team workflows :(

@jestdotty oooh I like the idea of splitting the front end, especially since managers and POs simply have different workflows/use cases than the people who are actually working on/refining the tickets.

@TeachMeCode JQL comes in handy in bigger organizations. We have some 500 users and around 100 000 tickets per year, being able to use JQL to customize views for different stakeholders is good for your sanity ;)

But that is because its not just one project but hundreds of projects.

For a single project, like firefox, you still do not really need all of jiras features.

But first us, any more simple system would require us to run multiple separate instances and the ones being part in multiple projects would then have to jump around and any time there is some overlap you would have to either spread the tickets out or use duplicate tickets.

As for slow, yes its not blindingly fast but with a set of dedicated servers with good performance its good enough.

its better than azure devops

@Voxera we’re a medium sized place that handles medium sized projects so i get. First exposure to jira was Sept 2022 and thought it was silly when I first saw it, i tend to giggle at knockoffs (JQL acronym is obviously a knockoff of SQL). Also found it funny bc to me it was like “look! We’re geeks too! We got a query language! See”? Actually after googling it looks more like a WHERE clause, it doesn’t resemble SQL at all (it looks totally boolean based at a glance). As you can tell i never actually used it

Jira, and all the Atlassian suit is trash because it is OVER COMPLICATED for very much nothing.

A simple thing would be to use an automation to update github and back, but, it requires so much setup and so much reading that it doesn't make sense in 2024.

Jira and atlassian are not know for making things simple.