Thanks everyone for your feedback on this issue. We appreciate the time you take to help us be better.

We are closing this Bug because boards with hundreds of cards will still load and can be used, they're just not as quick to load as we’d like. We use Bugs to track issues that prevent features being used as intended.

To be open about the problem, we’ve created a feature Suggestion to improve load times for large boards. Please watch this issue for updates, as we continue to work on improving performance over the longer term: JSWCLOUD-20971

Performance is a top priority for Atlassian, pease see our public roadmap on planned improvements.

https://getsupport.atlassian.com/browse/JST-602531

Hi everyone,

If you're working Kanban style (sprints disabled) for your next-gen project and have a lot of issues in the DONE column, we recently shipped manual board clearing to help you declutter the DONE column, so that your board can load up faster with less issues: https://community.atlassian.com/t5/Next-gen-articles/Introducing-manual-board-clearing-for-your-next-gen-Kanban-board/ba-p/1411958#

Regarding the performance on the next-gen board, improving the TTI (time to interaction) will be something that our team will be looking at in FY21, as performance and scale is one of the major focuses in the new financial year.

Regards,
Ivan

Product Manager, Jira Software

Hey Bryan I was curious if we heard any updates of bumping the priority to high?

Hi Bryan,

Actually I have a suggestion:
What if we can access issues in Kanban using a filter, like this? https:// XXXXX .atlassian.net/jira/software/projects/MM/boards/17?filter=10069

It will strongly narrow down the number that my teammates should see from Kanban.

Facts:

1. Now we can access issues in List View using a filter, https://XXXXX.atlassian.net/issues/?filter=10069

2. Now we can access issues in Kanban using an "assignee filter", https://XXXXX.atlassian.net/jira/software/projects/MM/boards/17?assignee=5e17adecbc8ab30e98eebc09
3. Now we CAN'T access issues in Kanban using a filter.

If you can do this, I think it will be a workaround for us.

Please let me know your thoughts on this, thank you.

Hey ya'll – I understand your frustration. Fair requests to bump up the priority to high – will look into this. I assure you – we're actively discussing solutions and the best plan of attack.

Please can you provide an update on this ticket. 

For many of my team it is becoming entirely unusable. 

Personally, when it takes 5 mins to write a comment it significantly reduces our efficiency/productivity. 

I echo the above users in suggesting that the priority be pushed to High based on your own criteria:

Priority 2 - High

A feature is unavailable, application performance is significantly degraded, or users job functions are impaired.

• the application performs slowly and fails intermittently

• application is functional, but frequently used gadgets or macros don't work

• specific editing features fail

Atlassian generally seeks to begin work on High priority bugs in the next sprint.

EDIT: I do not understand why you haven't provided us with any update or even any reassurance. 

Hi Bryan,

I'm sorry but I have to tell you, it is quite upset when I enter this ticket again and again, finding no real update here and the priority of this BUG is still "  Medium".

We've done everything we can to clean old tickets and I DON'T think this is the right way when we face a problem like this.

We love this Next-Gen Kanban so we choose to use it and make our 60+ users run on it.

And do we really have to try our best to clean tickets and keep the number less than, like 50, just to fit this BUG?

I think Jira is a powerful company and Jira team is a great team. You guys definitely can save the world.

So please, at least update the priority to "High".

logan-hood Is your team using a backlog? Is it too much to ask to throw the majority of the To-Do items in a backlog?

Why are there so many cards in the Done column? Would you benefit from the option to clear these off the board?

I would love to see an update on this, and after checking your bug fix policy, I agree with Logan, it should be recategorised:

Priority 2 - High

A feature is unavailable, application performance is significantly degraded, or users job functions are impaired.
Collapse

• the application performs slowly and fails intermittently

• application is functional, but frequently used gadgets or macros don't work

• specific editing features fail

Atlassian generally seeks to begin work on High priority bugs in the next sprint.

Bryan,

Can you pls respond all these user's comments (including mine) and concerns? Can we escalate this issue? No real update at all?

Hey there we are also experiencing this issue.  We are using a next-gen Kan ban board.  Some users are experiencing extensive load time.

Can we bump the priority to HIGH based on your bug policy? Application is degraded; users cant perform job function; no workaround. 

We have 5 statuses and they have the following in each.  

TO DO = 78

PRIORITY TODAY = 9

IN PROGRESS = 72

IN REVIEW = 33

DONE = 246 (this is capped at 10 in the view)

Any ideas to speed up the load speed?

We have over 1000 cards in our backlog and prioritising it or planning in meetings is just impossible because every click takes 30 seconds to a minute plus to load. Trying to drag things to change the order or move onto the board is incredibly laggy and causes things to end up in the wrong place.

Our teams have found the same problem! We are now using spreadsheets for planning meetings as it is impossible to be efficient with our planning as we have to spend so much time waiting for cards to load, drop down options to appear etc and I often find I end up clicking on the wrong thing because of the lag on my screen. Please fix this ASAP !!

Hi, we are also having difficulties on our project board with around 300 - 400 cards between the backlog and sprint. Everything is very slow to load and make changes to; this especially makes planning sprints a pain as people are waiting around in video chats for it to load which then eats into our working hours.

We use a backlog, and it's still slow, this doesn't allow us to break down tasks as we'd like to, as we have to compromise the number of cards on the board at any one time. Resolving this is a really high priority for our teams. It's frustrating to everyone to feel like the one tool that is supposed to aid their work is actually becoming the bottleneck.

I don't think we are using a backlog. We use Next-gen Kanban.

With most cases, yes, as many teams work in Scrum.

We find that even the backlog is super laggy.

Sorry again for the delayed response, ya'll. For those following this thread, I'm curious: are you using a backlog?

Hi All,

I'm getting in touch because my team (USA) has had some real issues with Jira being slow to load. We don't attach pictures or content to our cards and we've stopped having continuous epics but it's still a major pain point for the team. Cards take a long time to open and close, navigating the board often has a lag-slingshot effect, and oftentimes Jira simply won't load if we try to use it during video calls, which is problematic for our Agile working strategies. We do have just over 1000 cards on our board, but due to the volume of resources we produce on a monthly basis, we are not able to reduce this. Do you have any information that I can pass on to the team about support Atlassian can provide or a timeline for Jira to function at a faster pace?

Thanks in advance.

Hi Bryan,

It is nearly a month since this issue opened here under 20+ people watching, so far we have not heard any meanful update from your side yet, I agree that "new developments and features should be sidelined until you improve the performance of your service." as mentioned above. Can you pls escalate this and bring us some real progress update?

Thanks.

Hey ba3c070c5ffe we're investigating and prioritizing solutions. Updated the description. Feel free to leave more detailed comments in the meantime!

Hi Bryan,

Any updates on this issue?

Cheers!

Hi Bryan,

Could you update a little bit here?

Hi Bryan,

I also have some information to share with your technical team.

1. If you choose "hide cover image" on Kanban board, the performance is better but still quite awful;
2. If you use mobile app, there are no "cover image" there, the performance is MUCH better than it was in web Kanban

I think they are calling/requesting different APIs so if the engineer could take a little time to check these different APIs, maybe he can quickly locate the problem.

And I would like to meet with you guys too if you need more information on this. You know, before you make this public, my team and I investigated this a lot so I think there should be something we can share with you.

61521ce46dba I would love to! Feel free to find a 30 min calendar slot here: https://calendly.com/limbryan/30min

Let me know if the times don't work and we can find another time.

Hi Bryan,

To help with the exploring solutions process, we'd like to invite you to meet with us to review our board performance in real time.   

I think this would be the most productive way of sharing information, are you up for taking a look live with us?

FYI... performance on the IOS App appears less problematic. I don't have access to a Mac right now to check whether Jira Cloud for Mac app is also trouble-free, and there is no Windows app to check.

Looking forward to working with you on this!

Hi Bryan. 

Our entire org of 650 people are on it. Teams can range from 5-30 that and thus so are the projects. 

These are teams of all walks of life from Product to Marketing, Data to WebDev. 

Where possible, we are trying to break up these teams onto different projects, however in some cases it's just not possible. 

I'm glad performance is a huge focus, it would be so beneficial for us all. 

bc0d89663f0c Makes sense. How big is your team? How many users do you typically have assigned to issues on the board?

Performance is a huge focus area for us, so we're definitely working hard to address this

No, it's across the board and over all of the different projects within the same instance.

We only use Next-Gen in order to empower teams i.e. product owners, Scrum Masters etc. 

I understand that this may be a lot of effort. but the effect this has on teams' efficiency is massive.

It's the one thing that can make or break customer loyalty on SaaS, so please focus on getting it to perform.

Yup, sorry for the late update. We're exploring solutions and estimating the effort.

Out of curiosity, is there a particular column that has a lot of cards in it? E.g., "To Do" or "Done"?

My team has the same issues as Jacob and Mike.C. Not just the page loading on Kanban, EVERYTHING is slow. The fields themselves take 2-3 seconds to be able to enter data, drop downs the same, Comments fields 'Save' and it's near 10 seconds for the data to show up and the board itself has crashed several users browsers. Have seen instances where just trying to close a ticket takes more than 5 seconds. Not usable by my team in current iteration.

Hey Jira - Curious as to the outcome of "We're meeting on Tuesday AEDT to discuss", it'd be awesome if you can update us on any kind of workaround/ETA!

Thanks!

My team has the same issues that Jacob's team has. This is one of the biggest hitters against our productivity currently so it is critical for us too. Definitely a priority fix for me!

Hi there,

Many of our product teams are suffering on Jira due to the slowness of the boards. This is even the case with boards that do not have cover images on. 

We churn out a lot of issues, and so therefore it's really not possible for us to have less than 300 cards.

Having just implemented Jira and moved away from the free version Trello, we were expecting good performance for an Enterprise System.

I'd say that new developments and features should be sidelined until you improve the performance of your service.

Operationally, it means that we are losing efficiency and productivity because of the performance.

This is critical, please fix this.

Hi everyone,

Thanks for raising this bug. We're currently prioritizing this as necessary. 

Bryan Lim

Product Manager, Jira Software Next-gen