Hi,
We have deleted all the issues created in Jira. And now we would like to start afresh.
But then when i try to create an issue, the Issue Key takes the next sequence number instead of 1.
We want the issues to start with 1 now again after cleanup.
Is there a way to re-set the sequence to 1.?
Please let me know, its pretty urgent.
Thanks,
Harish
Delete the project and re-create one with the same key. You'll need to re-apply all the schemes and users in the new project.
Hi Nic,
Thanks for the response.
But it is very tedious process to delete all projects and re-create them . And more over assigning the users to each project takes more time.
May i know if there is any other workaround may be setting some configuration file.
Please advice.
Thanks,
harish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No. There's no other way in the UI.
You can do it directly in the database. This particular SQL is relatively simple and safe compared with other things people make a mess of with SQL - you set the pcounter on each project you need to reset in the "projects" table.
But, with SQL, there is no easy option - you have to stop Jira, get a backup of the database, prove it's a good backup, run the SQL, then restart Jira and re-index. (If you are only changing the counters in the project table, you do not need to re-index, unless you've got plugins that may be storing extra data about your projects)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Where is the SQL?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'd suggest starting again, rather than necroposting on a 5 year old question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since this was the right answer, it would make sense to have the response in this threat instead of now searching for SQL. But why bother consolidating.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know I am 6 years late with my answer... but I am going to give it anyway. When I needed to reset my projects issue key, I cloned the project and gave the clone a different name/key. Checked all the notification scheme, screen scheme, workflow conditions/post actions etc copied over, then deleted the original and gave the clone the original project name/key. Worked fine. Took 5 mins. Merry Christmas. J
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Jason for your comment, it helped me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.