Which is the maximun number of issues in backlog for Jira Cloud?

[adm-jiramapfre]

Which is the maximun number of issues in backlog for Jira Cloud?

We have a Project with 7622 issues in backlog , separated in several sprints. In each sprint appears de error message: Too many issues are trying to load

It will take you eons to scroll through mountains of issues.

[Kevin Bui · Accepted solution]

Hi @adm-jiramapfre - According to https://confluence.atlassian.com/jirasoftwarecloud/what-is-a-board-764477964.html, the maximum number of issues a board can load is 5000.

Boards can display up to 5000 issues at a time. If your board is trying to display more than 5000 issues at once, you'll receive an error message, and be prompted to update your filters.

I suspect the backlog might be the same. If your backlog has that many issues, it might be best going with @Jack Brickey's approach and splitting up your board into multiple boards. 

[Jack Brickey]

that is an absolute mind-boggling backlog. For sure a board would become unmanageable if it could load that many. Without understanding the reason for this it is hard to offer a suggestion w/ much meaning. However, some random thoughts...

• break your one board into many boards that focus on smaller components of work. Ideally you have a backlog of <200 issues
• Create a 3-stage board process: parking lot, stage one consider for dev, approved for dev. The parking lot would not be a board but simple a huge list of To Do work. Use labels, statuses or something else to move from Parking Lot to "Consider for Dev" and use that board's backlog to prioritize dev work. Use the final dev board for getting work done. 
• start closing issues that will never get done. :-)

[Grigory Salnikov]

Hi @adm-jiramapfre !

The best way is to limit the number of issues with the help of some filter that suits you. This information may be of help:

How to build a backlog filter query using JQL

Hope it helps.