I've got a problem with the counters of the Jira database. Every time I restart my server with the service Jira Software all the ID counters of the tables increase by 100 numbers. I need to restart my server and Jira a lot of time and in a short time I've reached the ID number 60000 of worklog, but I registered a few worklogs and there is a big fragmentation of ID! Is there a way to avoid it? How can I do it?
Nothing.
The question for me is why you care. It does not matter to the end-user what the counters do.
Thanks for the answer Nic. I only asked why this happens. I want to know only if this is just my problem, maybe because I changed some settings, and if this "bug" can create other problems. Anyway, I'll report it to Atlassian because it's logically wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's not logically wrong, it's been designed that way to avoid the problem of clashes in id. And it's irrelevant to the users.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.