Ticket_IDs are not continual

[Dominik Stahl]

Within our Jira, the Ticket_IDs are not continual.

those ids from one after another created ticket looks like: 247 , 379 , 623 , 1803 , 1852 , 1912 , 2132 ...

 

[Bastian Stehmann · Accepted solution]

Hi @Dominik Stahl,

welcome to this community.

Maybe this document may help, this covers a potential problem with randomly increased issue keys.

https://confluence.atlassian.com/jirakb/issue-key-increasing-randomly-317196053.html

[Dominik Stahl]

Hi @Bastian Stehmann,

thank you for your reply. I've checked the encoding - UTF-8 is enabled. 

Nevertheless this problem still exists. This SQL Exception does exist within the logs, but not for my newest tests.

[Bastian Stehmann]

Hi @Dominik Stahl,

if that error occurs (even if not on your latest tests), can please follow the steps here anyway, just to make sure it is not this problem:

https://confluence.atlassian.com/jirakb/sql-exception-while-updating-issues-or-importing-data-in-jira-applications-with-mysql-due-to-encoding-134480131.html

[Dominik Stahl]

HI @Bastian Stehmann,

i've checked those steps and added the following to the startup properties:

{code}

-Dfile.encoding=utf-8 -Dsun.jnu.encoding=UTF-8

{code}

The issue keys are still random.

[Dominik Stahl]

I've found the Problem. There was one E-Mail, with an Smiley, whitch Jira can not convert to a ticket.

Is it possible to rollback those massive falsely creates issue keys?

[Bastian Stehmann]

Great to hear that.

I'm sorry, but as far as I know, there is no way to do that.

[Dominik Stahl]

For others, who have the same problem, i've found a way to do that:

change the issue numerber on the database: "issuenum" on table "jiraissue", reset the counter "pcounter" to the last corrected issue number on table "project"

then reindex the affected project. 

If there are any attachments on those tickets: go to path of attachments on your host, e.g: /var/atlassian/application-data/jira/data/attachments/<your project>/<your Project number> and rename (move) the wrong issue id folder to the correct.