Need suggestion over 5k Issue limit in JIRA Board

[Zubair Ansari]

My Project has crossed 5k tickets in Backlog and it has thrown an error that it would take EONS to scroll through the issue.

As an temporary solution I have removed the closed tickets from "Query Filter" and that works for me but still I have something around 4700 tickets in Backlog.

I just need an Solution as how to sort out the 5k limit on board.

Thanks!!!

[Trudy Claspill · Accepted solution]

Hello @Zubair Ansari 

Welcome to the Atlassian community.

That limit is not configurable. You will have to adjust your board filter to retrieve less than 5000 issues.

5000 issues is an unwieldy number of issues to work with. It is unlikely that a backlog of 5000 issues can be effectively managed. Do you feel you've been able to effectively manage the backlog with so many issues?

I imagine the performance is also poor with 4700 issues.

Do you have some objection to breaking the backlog into multiple boards?

[Zubair Ansari]

@Trudy Claspill 

Thanks for the response !!!

I totally acknowledge with what you are saying and need to understand the same in terms of how to proceed on same. As I replied above.

[Trudy Claspill]

There are many ways you could subdivide the issues into multiple queries.

Do you use the Priority field to set general priority levels for your issues? If so you could create a filter for each Priority value and then create a board for each one of those filters.

Do you have multiple teams working on this project? Do you use some field in the issues to designate the team that "owns" to work? If so, then you could create a filter to get the issues for each team and then create a board for each team.

Do you use Components or Labels or Epics to group issues? You could use any of those in filters to get subsets of the issues and create separate boards for each saved filter.

[Zubair Ansari]

Thanks @Trudy Claspill for Resolution.

I got the transparency and will definitely proceed accordingly.

Regards,

Zubair Ansari.

[Kian Stack Mumo Systems]

@Zubair Ansari, 

Are you saying that you'd like suggestions on how to update your filter query to limit the number of issues returned, or that you'd like a way to bypass the error?

Thanks,

Kian

[Zubair Ansari]

@Kian Stack Mumo Systems 

Just trying to understand if I can limit the backlog count in existing board and is it possible that a huge chunk of backlog can be updated in another board.

For this, if you are saying I need a Query, then yes. I really appreciate your Support!!!

Regards,

Zubair

[Kian Stack Mumo Systems]

@Zubair Ansari, 

It seems like you were able to figure it out! If there's anything else, go ahead and let us know!

[Alastair Blakey]

I have a similar issue.  As a squad, we work on multiple projects, so need one board for the squad, covering those multiple project.

Our scrum Board filter JQL was:

project in (PMS, ALP1, FDP, CLD1, SRPMS) AND issuetype in (Story, Task, Sub-task, Impediment, Spike, Enabler, Bug) ORDER BY Rank ASC

Over a few years, we've created many issues, and recently we exceeded the 5,000 ceiling for the backlog.  So, to reduce the number, I modified the Board filter JQL, to:

project in (PMS, ALP1, FDP, CLD1, SRPMS) AND issuetype in (Story, Task, Sub-task, Impediment, Spike, Enabler, Bug) and created >= "2020/01/01" ORDER BY Rank ASC

The board now works again, in that it shows current and 2 future sprints, and backlog of issues not moved to sprints.

However:

The backlog page now shows all the issues we've ever recorded, which is extremely unhelpful.  It didn't do that before I changed the board filter JQL.
The assignee filter now shows 21 employees, from across the company, in addition to the 16 squad members who work on issues covered by the board.
 

Please advise!