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,

We're kicking off experiments for improving the initial load times to get to time to interactivity for the next-gen board and backlog. If you want to be part of the EARLY ACCESS program for the performance changes, please schedule an interview with me so I can get a baseline of the context of the way your team is working and the major problems you're facing.

You'll also be providing valuable feedback for our changes, as there are UX risks that we need to mitigate with these changes.

Please sign up for an interview here in September: https://calendly.com/iteong/next-gen-performance?month=2020-09

Regards,

Ivan Teong

Product Manager, Jira Software

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?