Issue with duplicate numbers in a project

JonB

Hello all - We migrated a project from another instance of JIRA, and we're running up against an issue where we're generating issue numbers in the 1500's, but there are issues that exist already in the ~1700 area - what will happen when we start to overlap? Will it break, or does JIRA automatically use the lowest available number to create an issue?

Nic Brough -Adaptavist-

That sounds like you used an adhoc script, or worse, a database copy, to "migrate" the project, and you've missed at least one of the counter updates you needed to do.

Short answer is that this is going to break when you hit that number range, and what you may need to do is go back to the backup you took before you did the migration (then you can do the migration again, properly)

You *might* be able to avoid the crash if you've only missed the one counter. But I can't tell you that it's going to work without knowing how you did the migration.

That fix is to stop Jira, update the counter directly in the database so that it's higher than the highest number in the project and restart Jira. (From memory, it's pcount on the project table, but check the other columns in that table too, I might have the wrong name of column)