Jira is a hot circle of garbage. I am going to check out Linear for my team because I can’t stand how slowly Jira pages load and how long it takes Atlassian to address documented bugs.
Anyone who makes general complaints about Jira like this a) works in a place where Jira has not been correctly configured or b) works in a place with a terrible internet connection c) works in a place where both a) & b) are true or d) doesn't have any idea what they are talking about. P.S. what exactly is "a hot circle of garbage" other than a mixed metaphor?
> works in a place with a terrible internet connection
That excuse just doesn't hold up when any comparable issue tracker (or web app in general) works fine on the same internet connection.
JIRA, just like any other Atlassian product has a slowness to it on every click and navigation that makes it feel like you are wading through molasses.
We use Jira cloud, so if it is misconfigured, blame them. My internet isn’t great, but I will anecdotally note that Atlassian sites are the only ones that ruin a videocon connection. As for your general criticism comment, glass houses.
- they’ve had a ticket to hide completed epics from the roadmap open for over a year.
- their user management is a unmitigated disaster. God help you if you use bitbucket or Trello (although Trello users are getting integrated in after 4 years!).
- it took me literally 2 months of help desk tickets to figure out how to get an invoice. The former billing poc was fired, and even though I was the site admin, I had to recreate his account in our SSO, log in as him, and then assign the role to me.
- have you tried to set up even a slightly customized Jira Service Desk?
- want to expire “done” issues faster than 14 days? Pound sand.
- I could keep going, but what’s the point? Atlassian is a bunch of decent products drowning in scope creep, terrible cross-product integration, and a painfully slow development cycle that is focused way more on cosmetic features that fixes their trainwreck of a dumpster fire.
There are myriad ways to misconfigure a cloud instance of Jira. You thought I was referring to the configuration of the actual web app I suppose. That's kind of a silly assumption but gives me a lot of insight into what you've said here...
A quote from a funny TV show still doesn't really make it a thing, does it?
If it's not, there probably is a way to do what you are trying to do that you just don't know about.
I work at a very large organization. The user lookups in Jira are lightning fast & the permissions are granular for a reason.
Can't help you with your billing problems but it kind of sounds like a "you" problem.
I have fully configured a Service Desk instance, yes.
It sounds like maybe you aren't actually using the release feature & or that maybe you don't know how to write JQL queries or maybe I don't know anything about the amazingly advanced way you are trying to use the features. "Hey doc, my arm hurts when I do this?" The doctor says "Then don't do it."
I could keep going too but it would be a waste of my time to try & have a reasonable discussion on something which you have prononuced your verdict: "Atlassian is a bunch of decent products drowning in scope creep, terrible cross-product integration, and a painfully slow development cycle that is focused way more on cosmetic features that fixes their trainwreck of a dumpster fire."
I‘m working for 2 companies atm where one uses Jira and one uses Linear.
Doing anything in Jira / confluence is really slow. It’s a nightmare to navigate and it seems like every time I click on anything, it takes 2-3 seconds to load.
It’s really hard to explain but I guarantee you that if you tried linear out, you’d “get it”.
This isn't quite true, as others have mentioned throughout the thread, JIRA Cloud is noticably slow to use, to the point where doing non-trivial stuff is frustrating - page loads take several seconds, and most operations require a page load. I'd expect their hosted version to offer the best performance, but apparently it doesn't. It's not unusable or anything but it's definitely a very sluggish feeling experience compared to a lot of the SaaS we are used to.
Which would be a fairly rubbish take, because when it's my workflow, it's MY WORKFLOW. What they might mean is "I have not set up my workflow according to Jira's needs" which is entirely Jira's problem to solve.
