-
Suggestion
-
Resolution: Fixed
-
1,163
-
Hi everyone, as promised in the last update, we have now also shipped the new experience for team-managed projects.
Team-managed Jira boards with more than 5,000 issues will now display the first 5,000 issues based on the board filter settings.
You can read more about issue limits in team-managed projects here.
With this final update, we are now closing this ticket and would like to thank everyone for their patience and for sharing invaluable feedback with us.
You can still continue sharing your thoughts and feedback about the new experience with us through community.
Best,
Megha Chaudhry
Principal Service Enablement Engineer - Jira Cloud
Hi everyone, this is Megha from the Jira team. I’m pleased to share that we have updated our board and backlog experience for company-managed projects.
A Jira board that contains more than 5,000 issues will now display the first 5,000 issues based on the board filter settings.
Read more about how this feature works in my community post.
At the moment, this update is only for company-managed projects. But we’ll be rolling it out to team-managed projects as well in the coming weeks.
We thank you for your patience as we work through these changes.
Best,
Megha Chaudhry
Principal Service Enablement Engineer - Jira Cloud
Problem Statement
Filter Query with more that 5000 issues displays "Too many issues are trying to load":
Suggestion
Allow more that 5000 issues to be displayed on the board
Notes
Per release notes in December 2017:
https://confluence.atlassian.com/cloud/blog/2017/12/atlassian-cloud-changes-dec-11-to-dec-18-2017#AtlassianCloudchangesDec11toDec18,2017-jira.software
Boards display a maximum of 5000 issues
To reduce slow load times and accelerate your Jira experience, boards will now display a maximum of 5000 issues at a time. If your board tries to display more than 5000 issues, you'll be prompted to update your filters.
Workaround
Company-managed
The currently available workaround would be to create more than one board within the same project, splitting the current unique board and applying to each new board different filters on Board Settings > General.
For example, for one board you may have only issues of a specific issue type or which contains a specific label.
Of course, this will depend on your process, so you would need to check which field value/specific details of issues could be used to create separate queries.
- depended on by
-
JSWCLOUD-18037 Next-Gen board does not load issues when there are over 5000 issues
- Closed
- is related to
-
JSWCLOUD-5914 Issues raised with Bonfire do not show up on GreenHopper Rapid Board
- Closed
-
JSWSERVER-5914 Issues raised with Bonfire do not show up on GreenHopper Rapid Board
- Closed
-
JSWCLOUD-20432 Increase issue limits for Roadmap view
- Closed
-
ACE-4758 Loading...
-
ACE-5012 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
MOVE-1746638 Loading...
-
ENT-1367 Loading...