Split jira instance after exceeding 200k issues

[Heshan Manamperi]

Hi All,

Atlassian has recomended split jira instance after exceeding 200k issues. Our JIRA instance also exceeding 200,000 issues and I need to split it to another instance.

So what is the industry practice for split JIRA instance after exceeding 200k issues?

If I did't split JIRA instance what will be the outcome after esceeding 200k issues?

Regards,

Hesh

[Norman Abramovitz]

Please read what has been written already on this subject.

https://answers.atlassian.com/questions/10402/who-has-experience-with-200k-issues-in-jira-was-performance-degraded

https://answers.atlassian.com/questions/43974/splitting-a-jira-instance

[Norman Abramovitz]

If you decide to split your Jira instance, here are the directions.

https://confluence.atlassian.com/display/JIRA/Splitting+a+JIRA+instance

[Nic Brough -Adaptavist-]

For the record, the 200,000 is an old limit, I heard around Jira 3.4ish. I suspect it's crept upwards with all the various improvements Atlassian have made.

Also, I've worked on much larger installs - over a million issues in one. With care and attention, it can be made to work very well, but going over the threshold will cause you increasing maintenance time/cost, lower performance and stability. But there's no easy way to give you a hard number. It depends on your hardware, network, user numbers, complexity of your data, what the weather is like and so-on (yes, the weather comment sounds facetious, but in one place I worked, rain caused problems, because we were overloaded and the users came inside and worked instead of going out to play in the sunshine)