Is it possible to reset the issue key number?

[Samandeep Singh]

Hi,

Once the issues are deleted, is their a way I could re-use those keys?

For example as of now Project-1 to 10 are created and suppose if I delete all the 10 issues(due to some errors while importingissues from import wizard) then the new issues are numbered from Project-11. I want it to be from Project-1 again. Any Suggestions!!

Thanks

[Haran Kumar · Accepted solution]

@Samandeep Singh  , As Mirek  mentioned there is no possible way to directly get back the key even after deletion of current issue. And creating new project for advanced projects will be tedious. 
Instead there is a wierd way that can help you in projecting issues . Create a new Project and create issues over there and map the existing issues accordingly to it . Though, its not a presentable idea , this might be one of the way . 

Regards.  

[Mirek · Accepted solution]

No. You are using Cloud so it would not be possible (unless Atlassian Support would do it for you). On Server it is possible by executing some database queries. The only way on Cloud is to start a new project from scratch but I do not think it is a good idea when project is in advanced phase..

[Samandeep Singh]

Dear All,

Issue deleting will not harm me that much because I am at the beginning of the project and creating Tasks and Sub-tasks for follow-up.

Work has not started till now on the project.

Right now my priority is to just represent the project in a more presentable manner.

[Haran Kumar]

@Samandeep Singh  , if you don't mind recreating issues then the best suited option will be to create a new project and recreate tickets. 
On that note ,you can create required tickets in new project and then later delete the existing tickets , thereby ensuring you dont miss any tickets. 

[Samandeep Singh]

Thanks Haran,

Yes, I will create a new project now. 

[Joe Pitt]

Do not delete issues. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. Deleting issues will come back and bite you when it is the most inconvenient. I suggest closing with a resolution value of Deleted anything you want to delete. I implement a special transition only the project lead can execute and it requires filling in a reason field from a select list (such as entered in error, OBE, Duplicate, Other) and explanation text.

Deleting issues destroys historical data. Missing issue numbers will eventually cause a question about what it was and why was it deleted even if it was done properly. Missing data always brings in the question of people hiding something that may have looked bad.

The only viable way to restore an issue is to create a new instance of JIRA and restore a backup that has the issues. Then export them to a csv file and import them to your production instance. You will lose the history.