Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira Cloud performance with over 1M issues

Hi all,

We're researching if we should migrate some of our operation as issues managed in Jira, and are worried about possible performance trouble. I found a sizing guide for Jira Server but not for Cloud:

We plan on creating about 1M issues, possibly on the same project. Most of the issues will not be resolved. We won't have many users and will have a few dozen custom fields.
The number of issues will grow with time and may reach tens of millions.

How will this affect the overall performance of the board and ticket handling?
Is there a sizing guide for Cloud?

Thank you.

1 answer

1 accepted

0 votes
Answer accepted

Hello Shay,

Thank you for reaching out.

As you may know, Jira Cloud runs on Atlassian Servers, so a sizing guide would not give you any relevant information on what you should be measuring against it. Explaining it better:

JIRA Cloud has different plans that will adapt to your current necessity (2GB, 250G, Unlimited), giving you the storage and resources you need to achieve your goal. You can check the documentation below to know about the plans and how you can track your current storage in your site:

Storage for Jira and Confluence Cloud 

As you can see in the documentation, even if you reach the storage limit of your current plan, we won’t cancel your subscriptions or remove any data, as long as the usage is in accordance with our acceptable use policy.

That being said, storage does not cause performance issues and Jira is completely able to handle millions of issues without any performance gaps. Usually, only a huge usage of external scripts for bulk operations and Automation could cause such overload, although this is far from common.

Let us know if you have any questions.

@Petter Gonçalves

Does Atlassian recommend limiting the number of active issues in a Service Desk project?  Given performance impacts and time to reindex associated with SLA changes, Automation, etc., what is the recommended/suggested project size before archiving should be instituted for Service Desk projects?

Hello @Robert Davenport

There are no limits or recommendations for archiving projects in Jira since the number of issues in a specific project will not affect the performance, but yes the total storage data you have in your site.  In fact, the project archiving is a feature created to keep the search and organization of the issues in a better format, not to prevent any performance issues.

That being said, keeping your data storage under the limits of your plan as described in the documentation above should prevent any possible performance issues.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you