Reset Issue Key on Jira Cloud Environment

[rsstorey]

I'm configuring a project on Jira Cloud that is integrated with external tools.  Is it possible to reset the project counter so that issue keys start from 1 or another number after deleting the test issues?

I've seen that there are solutions for server or data center Jira environments but nothing for Jira hosted on Atlassian Cloud.

Appreciate any help anyone can provide.

[Nic Brough -Adaptavist- · Accepted solution]

There is no way to do this on Cloud, sorry,.

[Angel Maenza]

This really should be an option - I've seen so many questions just like this one. It's pretty obvious users want to start fresh after creating test issues for set up purposes.

[KarstenK]

Hi. It is possible on Cloud!

1. Export all items from the project as CSV
2. Use Excel to edit the CSV (work on a copy!) and alter the values in column "Issue key". Do not change other values!
3. Export the file from Excel as UTF-8 CSV
4. Go to Jira > System Settings > External System Import > CSV
5. Choose the new CSV file as import file and set delimiter to ";" > Go Next
6. Choose the project > Go Next
7. Now you have to map the columns of the CSV to the Jira fields:
   1. Map columns "Issue key, Issue id, Summary"
   2. Set the check-mark "Map field value" on line "Issue id" only (This is important for the import job to not add the import as new issues but to overwrite the existing issues where the issue id maps)
   3. Do not map other fields
   4. Go next
8. Validate the import to see if the number of imported issues is correct. In case of problems go back to adjust the mapping
9. Execute the import
10. Check the result in the project

❗ Be careful if issues are linked to epics or to other issues. You may have to set the links again to the new Issue-Keys. Also check you filters and plugins

❗ You should try that procedure on a copy of the original project first to be sure about the correct result.

[Nic Brough -Adaptavist-]

Nope.  This won't reset the key, it will edit the existing issues in the project if they still exist, or create new issues, with the next sequence number if they do not.

[KarstenK]

I did it myself and it worked. 

[Vanessa Lourenço]

I did it and it seemed ok, but when I created a new item, it followed the sequence considering the deleted items

[Nic Brough -Adaptavist-]

I am sorry, but it remains the same answer.

[Vitali]

Hello,

No, but you could create a new project with shared configuration of the current one and migrate the issues over to the new project.

Make sure to have the same component/s, version/s, and other project specific configurations in the new project before moving the issues. 

After migrating, you can delete the original project and change the project key and name of the new one to be exactly as it was. 

Best regards,

Vitali