Hacker News Reader

Comment by mark_and_sweep | Hacker News Reader

The biggest issue, in my experience, has always been its performance. Perhaps I have only worked in organisations that have completely misconfigured their Jira instances or the servers are underpowered, but even with the Atlassian Cloud, I am used to waiting 10 seconds to move a ticket from one column to another. Or add a ticket to the backlog, click the backlog, ticket isn't there yet, refresh the backlog, it's there. Add a ticket to the sprint, click the sprint view, ticket isn't there. Refresh the sprint view, it's there. This sh*t. Every day. Is driving me insane.

I don't want the perfect tool, just one that isn't horrendous.

View on HN

Yes to this, the performance is terrible and the UI/UX is extremely janky.

There is a lot of fault on the companies who are implementing bad configurations and multiple setups for different teams definitely adds to the complexity. To have a 'lite/light' stripped down version which is purely functional and not bloated with drag and drop events etc would be a really nice to have.

Absolutely. I worked with a lot of different tools and Jira is as good as any other project management tool. But it just didn’t feel as responsive as, for example, Linear.

Asana was just as bad as Jira in terms of performance, with the added feeling that somehow something was always happening in the background…

I agree. Most of the workflow jank could be forgiven if I didn't need to wait double-digit second loads frequently.

I took a look at this a few years ago when considering a tool. Back then it turned out every button on a ticket needed to query the server as to whether it had permission to show. Just a terrible architecture.

We went with Asana. I miss the ability to create epics and do proper sprints, but at least the things load when you click on them.

I used to be a pretty big Atlassian fanboy. I'd default to most of their tools when they were available.

Before the new UI came around in ~2017 it performed pretty well and if you were judicious with customization it was easy to use. Everyone knows Jira so it was easy to get new people started with it. Then the redesign came out.

I opted in for a bit when it was in Alpha but bailed because I had trouble getting my job done in trivial ways. I'm normally pretty accepting and friendly to new UIs, even if its rough at first. I generally accept that I won't like most at first because it disrupts my workflow in the short term. Usually once I relearn the project its for the best. Not with this one. It's just so damn slow. It's terrible.

I'm not in a position where I pick our project management/documentation tooling anymore, but if I was I don't know what I'd pick. It used to be that I wouldn't think twice, now Jira isn't seriously in the running anymore. I think notion has beaten out confluence even if I'm still not in love with it.

> Perhaps I have only worked in organisations that have completely misconfigured their Jira instances or the servers are underpowered, but even with the Atlassian Cloud, I am used to waiting 10 seconds to move a ticket from one column to another.

There must be some sort of misconfiguration going on here, as I never have this experience in Jira Cloud. Your opinion is a common one so I'm not discounting it, but with "New Jira" as I call it (the Team-based projects), this never happens to me.

But in general, I agree that Atlassian should primarily focus on performance fixes, it is by far the most common complaint.

100% this. The worst software in the world could be forgiven if it were fast. Ours was self-hosted, but it's depressing to hear that the cloud version isn't much better.

Performance is vastly improved in last few years. Until 2020, Jira Cloud was really slow.

Atlassian changed their strategic focus from on-premise to cloud, and they are making lots of improvements, including performance.

Reply on news.ycombinator.com