Hi everyone,

Thanks for your feedback on this issue. We appreciate the time you take to help us be better. The current functionality of Next-gen boards with > 5000 issues is expected as Jira Software boards and backlogs are limited to returning 5000 issues. Next-gen users who hit this limit will now be shown an error message instead of an empty board/backlog.

To be open about the problem, we are closing this bug and ask that you instead watch/vote the Suggestion for this feature and track our progress: JSWCLOUD-16259

I found my way here through Jack's assistance on another thread (https://community.atlassian.com/t5/Jira-Software-questions/Board-view-for-next-gen-project-showing-Your-board-has-too-many/qaq-p/1494695) where our board also had a large number of total issues over 5,000. However, many of them were in Done status, enough that the board would load without issue.

We added a new status and suddenly the board displayed an error and we could not get to the board to perform any adjustments. (Edit: the board would explicitly show the error message in the thread I linked above, rather than simply failing to load issues.)

I was able to restore access to the board by using the REST API to capture detail on 1,500 issues and delete them from the board, but I will need to restore them at some point soon. (For those wondering why we have so many active issues on the backlog, they're a combination of task>subtask groups where we're using Jira to assist with time tracking on the component work subtasks.)

However it's not clear what we need to do to ensure the board continues to function when I reload the 1,500 tasks. The fix for this bug should create some mechanism by which you can manipulate the board's statuses even if you can't view the board itself.

Thank you, Jack, as I agree this is a huge "rework" during the midst of our project when we rely on reporting from Jira (NextGen!)

While this doesn't personally impact me as I don't use NG to any capacity where this would hit me I did want to raise another finding w/in the Community (see post here). the issue raised was that if you have a large quantify of Done issues and add a new column then the new column becomes the Done column and now all the old Done issues will visible in the board unless your number of done drives you to more that 5000 issue in board. The poster had to bulk move issues from one project to another so they could correct the board. Yikes....certainly not a Medium bug.