New Jira is dead slow

[Vimal George]

JST-367472 -> low priority ticket??? Really???

Productivity of the Jira user has reduced to 50% at least, by your new update.  Just for a new UI you have compromised the performance.

Good point is that, it is the gateway for your competitors. Waiting for new  products in Market

[Steven F Behnke]

No one here can see JST issues - they are private support requests.

[Vimal George]

https://jira.atlassian.com/browse/JSWCLOUD-16647

This one is created based on JST-367472 

[Steven F Behnke]

LOL.

Agile boards are designed for a few hundred issues. They have never been performant above 1000 issues. When I used to consult I was telling people this all the damn time. It's a SCRUM board. It's designed for SCRUM. 3000 tickets is the ANTITHESIS of SCRUM.

I took a consulting gig with an aerospace company who was trying to cram 5k issues on a board and I told them straight up from the get-go that it was not going to work.

[Nic Brough -Adaptavist-]

I seem to remember a study showing that if you present a human with more than 300 lines of data, they simply can't use it usefully.  They need summaries, and to be able to focus on the important bits easily. 

When I see people with more than 250 issues on a board, the conversation needs to start with "your board is too complex, how do we make it usable?"

[Vimal George]

They never been performant above 1000 issues??? 

May be you havent seen the previous version with more than 1000 issues. That was working smoothly.

Somehow, Jira has limited the flexibility, may be above theories can support them. 

If this issue is raised recently, that just mean that there was something usefull in the previous version.

Also, it just doesnt work on theories. Focus was on how it could work before and how they have blocked that usabilty now. (Not blocked, infact introduced new bugs for Jira itself)

[Danyal Iqbal]

Is it a cloud instance?

[Vimal George]

Yeah. It is a cloud instance

[Danyal Iqbal]

Atlassian cloud is notorious for (unsolved) performance issues. You should consider migrating to a server instance if there is anything important in your cloud instance or you could try remedy:)

+1 for bug

-1 for cloud

[Vimal George]

Funniest fact is, it was working almost smooth before the update