The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
The ideal maximum number of issues/tickets per Jira project to maintain optimal performance?
Any documented thresholds where performance degradation typically occurs (e.g., 50K, 100K issues)?
Our team manages several large projects and wants to:
Avoid slowdowns in filters/dashboards
Prevent timeout errors during bulk operations
Plan archiving or project splitting strategies
We’ve reviewed Jira Cloud Performance Guidelines but would appreciate clarity on:
Whether these limits differ for Jira Cloud vs. Data Center
How custom fields/workflows impact these thresholds
Thank you for your expertise!"* I would like to ask a question.
In the Jira application, how ideal is it to have ticketing within one project? Can anyone explain the maximum number of tickets within one project so that it does not interfere with the performance of the Jira project itself?
28 comments