I'm working in a JIRA project that is approaching 60,000 issues. The reason the number of issues is so high is because we are using one central JIRA project for many different products.
Is there a limit to how many issues should be in any one project? Does responsiveness slow down as the number of issues in the project increases?
Hi Kevin,
Currently, there is no limit of issues in a project or on the instance, but yes, if a project has too many tickets, mostly open tickets (without resolution) it may affect reports, queues and also it can take a little longer to search for tickets on Issues and filters > Search issues, but only if there are too many open tickets on a project.
60k issues are fine for now, it won't affect the performance, but always make sure to add a resolution on all tickets, I don't know if you are using Jira Service Desk, but I'm telling you this because the reports and queues usually show unresolved issues.
As a best practice, if your instance has old tickets you can export the CSV and then delete the tickets of the instance.
Also, it's important to manage the attachments to do not exceed the storage limit that may cause some slowness.
You can find more information about the storage policy on the link below:
- Atlassian Cloud storage policy
Hope this helps!
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.