I have seen some posts that indicate instances with over a million tickets exist, I am just trying to verify if there is indeed a max limit on issues. I work in a large corporation that is currently using a cluster of servers for Agile projects. We are considering creating a new instance for a special application, and need to know if there are any constraints on the total number of issues.
Hi @Michael Sevcovic ,
welcome to the community!
Jira Data Center has not a specific limit for issues. Based on the following scheme https://confluence.atlassian.com/enterprise/jira-data-center-size-profiles-955171062.html, a JIRA instance with more than 600.000 tickets is considered a large instance.
Over 2.000.000 tickets is considered an Xlarge instance.
For an enterprise company, my suggestion is to scale nodes at your convenience. Moreover, you have to setup and tuning database so it can store all information.
On the linked URL you can retrieve information about how to determine hardware requirement for your instance.
Hope this helps.
Fabio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am aware of several places that are well into @Fabio Racobaldo _Herzum_ 's definition of "extra large" - one is over 11 million issues. It's a big DC install and very large, and they are making full use of archiving for projects that have finished but need to remain searchable. But 11 million...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know the answer is a bit vague, but I think an example of "huge number of issues and the business is still using it for all the tracking because it's working fine" is appropriate.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Community!!
There is no Constraint!! You can have as many as you want
Technically your setup should have capabilities to handle requests from a large number of users and even DB resources play an important role here!!
You could follow the Guide here as an example
Thanks,
Pramodh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
There is no restriction in the amount of tickets.
In my experience you will have more troubles with a relatevely small amount of tickets with a lot of different workflows and other configuration schemes than an instance with a lot of tickets and a low amount of workflows and config.
Of course your reindexing process will take more time with a lot of tickets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.