agree there will be performance issues blocking the road before any one gets there, wanted to quick check if there is any other upper cap put by them on number of issues in the syste,.. anyways checked in table jiraissues as well where they store id and pkey.. id has datatype of number(18) which will verryy high from any organization's perspective. Thanks ofr your replies.
The ID is Long type, the answer would be (2^63)-1 as per javadoc,Long.MAX_VALUE = 9223372036854775807, Long.MIN_VALUE = -9223372036854775808
As Nic says you'll be dust before JIRA gets there (I dont believe there are any coded numeric limits on the ID, the reason being that you'll find scalability issues oh, just a little while before you get there), I can just imagine logging an issue "its the end of the world":
Imagine 1K per issue. Thats still 8388608 TB of comment data :D
I really don't know, but you don't stand a chance of getting anywhere near it. Millions is probably the easy, and very very understated answer. I'd guess at the code limit being whatever the highest number you can put in a java "long" object, but it really is one of those utterly pointless questions - the answer is irrelevant because you'll never get close to it.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs