Jira OpenSearch- 10,000 Issue Display Limit for Boards and Backlogs

[#1]

As part of the OpenSearch project—our strategic initiative to unlock greater scalability, enhance search capabilities, and eliminate indexing issues in Jira Data Center—we’re introducing a new limitation on the number of issues that can be displayed on boards and in backlog.

Starting with version 11.2 of Jira Data Center- OpenSearch GA (General Availability) release, boards and backlogs powered by OpenSearch will be capped at displaying 10,000 issues. If your results exceed this limit, a warning will be shown in the UI.

Lucene’s behaviour will not change in Jira 11+, and while we plan to introduce the 10,000 issue limit next year, we will first observe the impact of this change in OpenSearch before announcing the rollout.

This update is a step in enabling Jira to scale for the largest enterprise customers, improve overall search performance, advance the quality of user experience, with quicker page rendering and prevent the indexing bottlenecks and outages that have impacted teams as their instances grow.

---

What’s Changing?

• OpenSearch-powered boards and backlogs will display a maximum of 10,000 issues by default.
• If a board or backlog contains more than 10,000 issues, only the first 10,000 (based on sorting order) will be shown, and a warning message will alert you that the limit has been reached.
• Admins will have the option to increase this limit, but should be mindful of possible effects on memory consumption and search performance.
• This update ensures consistency between Jira Data Center and Jira Cloud, providing optimal performance and seamless user experience across platforms.

---

Why this change?

• This limit is being introduced to improve performance, reliability, and scalability for all customers
• Large boards and backlogs with tens of thousands of issues can cause significant performance and usability problems, including slow page loads and browser crashes.
• The new limit helps ensure a positive experience for all users, and aligns the Data Center with Cloud best practices.
• This change is necessary to support the new architecture introduced with OpenSearch, where the Search API layer enforces a 10,000 issue display limit to ensure performance and scalability.

---

What if you need to work with more than 10,000 issues?

• You’ll still be able to access all your issues using Jira’s search and streaming APIs. While the board and backlog views will be capped at 10,000, advanced search and streaming methods can return larger result sets for reporting or automation purposes
• A warning will appear if your board or backlog surpasses 10,000 issues.
  • Increasing the limit is possible, but it comes with trade-offs: higher memory consumption and slower search performance. The related documentation will provide detailed guidance and recommendations.
• To ensure the best user experience with the 10k limit, if your backlogs or boards go over this threshold, we recommend adjusting your board filters, splitting large projects into multiple boards, or archiving completed issues to stay within the limit.

We want your feedback!

Do you have a use case where you need to display more than 10,000 issues on a single board or backlog? Please share your scenarios in the comments—your feedback will help us understand real-world needs and guide future improvements.