Nothing but vague/general responses such as "generate 500k issues and find out" or pointers to the same JIRA sizing guide that references nothing regarding database sizes? Why not even a rough estimate based on your own testing environments that can give people a general idea or starting point?
Because it really is totally variable.
Look at an issue. It is possible to set up an issue that is as small as a single line in a tiny handful of tables. If it's just got a summary field and nothing else, then only jiraissue and a couple of workflow tables make up the whole thing. Then a line in the history to say "it's been done" is two more lines in the history tables.
Then you take something like a change control Epic. With forty fields, mostly starting blank and being added to over time as it goes through the CR process, lots of reassigning, asking people for comments and updates, a pile of attachments, and so-on.
The second issue is going to be orders of magnitude larger than the first. I can show you two JIRA systems with 10,000 issues, 50 users, and 20 projects. One of them has a database six times the size of the other. Any estimate given based on one of those, is almost certainly going to be misleading you on your sizing.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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