nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

duplicate issue numbers found

Andrew Thorne

Hello,

For one of our project, somebody created some new issues lately and somehow they have been entered in to the database with the same issue number as an existing issue number.

My question is what can be done about it?

JIRA will not allow us to open the issue anymore, probably because it is receiving more than 1 issue id when searching for that issue number. This means that I cannot delete one of the duplicates and then recreate it (hopefully, then with an unique issue number).

There are 14 duplicate issues in total.

The people who look after the servers are not keen (read: refuse) to manually edit the database. So any solution that does not involve hacking the database will be considered.

We do have Botronsoft's Configuration Manager installed, which we used for merging 2 JIRA instances at the end of last year. Unfortunately our super-tech guy has left but I was wondering if that could be used: Export the project, delete the duplicate records, delete the project, re-import the project.

We are using JIRA 7.3.6

Thanks for any advice you are able to give.

Andrew

Accepted answers

Kristian Walker _Adaptavist_

Hi Andrew,

Thank you for your question.

I can confirm that the data import functionality provided by Project Configurator uses the built in Jira Data Import functionality meaning that in order to import a project the Project needs to be empty on that instance and its key needs to be unique.

The reason for this is that Jira stores a mapping to historic project keys in the project table in the database in order to maintain project aliases when a project key is renamed.

This means that that here you will be able to export the complete project and re import it as long as the current project is deleted from the Jira instance before running a re import.

As mentioned by Alex we recommend taking a clone of your Jira instance to test this on first before you run this operation on your production server.

One other alternative I would suggest trying is to see if you can search for the duplicate issue using JQL in the issue navigator and if the issues are found to try moving one with of the issues to a different project using the bulk edit option to change its issue key. Once It has moved projects you should then be able to move it back to the original project where Jira will allocate it a new issue key.

If this answer has solved your issue can you please accept it in order to mark this answer as correct for users who are searching for a similar issue.

Regards,

Kristian

All comments

Alexey Matveev

Hi,

Configuration manager does not migrate data between instances. The plugin only migrates configuration. But in your case the problem lies within data.

You can try to use Adaptivist Project Configurator. It can migrate data and maybe it will change issue keys. But on the other hand if it changes all the issue keys, you can have problems if you somehow make references to issues by keys. You should try first on a test instance and make sure, that everything works correctly.

Kristian Walker _Adaptavist_

Hi Andrew,

Thank you for your question.

The reason for this is that Jira stores a mapping to historic project keys in the project table in the database in order to maintain project aliases when a project key is renamed.

This means that that here you will be able to export the complete project and re import it as long as the current project is deleted from the Jira instance before running a re import.

As mentioned by Alex we recommend taking a clone of your Jira instance to test this on first before you run this operation on your production server.

If this answer has solved your issue can you please accept it in order to mark this answer as correct for users who are searching for a similar issue.

Regards,

Kristian

Andrew Thorne

Hi, Kristian,

Thanks for your reply. I was able to solve the problem by moving the issues to another project and then moving them back. It is a bit messy, if you ask me, but it is easy and it works! (That's the most important thing.)

Thanks again for your help.

Andrew

Kristian Walker _Adaptavist_

Hi Andrew,

Thank you for confirming that your issue was resolved.

Can you please mark my answer as accepted so that other users with the same issue can easily find this as the correct solution.

Thanks

Kristian

Sharon Dodoo

Hi All,

I am facing some sort of similar issue about duplicated ticket numbers. The genesis of the whole challenge started when it was detected that the volume on which the jira data sat was getting full. A snapshot was taken. The very next day users could not long into jira anymore. The snapshot was installed back and users were able to login. Now when they create tickets, other users can also create the same ticket number.

Can someone assist me resolve this issue.

Thank you

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

issue

jira

jira-server

duplicate

botron