I am facing this whenever I create a sub-task of any kind whether it's sub-task under an user story or an user story under an epic. The number is added incrementally like SO-1, SO-2, SO-3. So, I am not able to distinguish between sub-task and task easily.
JIRA uses the project code and a number for the issue key. That's it, I'm afraid.
Most people use the icons to show that an issue is a subtask. It's also exposed in the summary and breadcrumbs in a lot of places.
Hi Nic. Thanks. Ok I got what you told. But, I want to bother you with one more thing.
Suppose I create a story. It is denoted as SO-1. I created another story as SO-2. Now, I deleted both SO-1 and SO-2 with the intention to start afresh. At this point, what I experience is when I create a fresh new issue, JIRA automatically the ID as SO-3. But, I don't want that. As I am starting fresh, I want it to be SO-1.
Each new issue increments the project counter. JIRA doesn't go looking for empty spaces in the sequences (and with good reason - it's slow, pointless and the holes in a sequence are still information, even if there's no data), it just uses the next number.
In older versions of JIRA, you can reset the counter by deleting the project and recreating it. Newer versions preserve the information that there was a project there, so you can't create new ones with a key you had before.
Your only option in later JIRAs is to reset the counter by amending the database, after making 100% sure that you deleted all issues that were in that project (even if they've been moved to other projects, you still need to delete them)
If a user has created a total of 3 issues, s/he can delete all the issues without much pain and can start afresh by amending the database as you told. But what if, if a user has created 100 issues such as SO-1 to SO-100 and wants to delete SO-99. That means, after that the count will go like SO-1 to SO-98, SO-99 missing forever, SO-100 and so on.
And, it would be much pain then to delete all the 100 issues and amend the database to adjust the numbering.
Could you please let me know the procedure to reset the counter.
No, as I already said, it's a simple counter. But you don't have to reset it to 0, you can set it to anything you want.
You must delete all the issues created with a number higher than the one you are going to set the counter back to. (For moved issues, you could destroy the issue history instead of deleting them though. More complicated to execute, but possible)
Stop JIRA, take a full database backup, then go to the project table - there's a field in there with the counter in it (I think it's pcounter). You need to set that to the next number you want to use in the project (Edit - from memory, that might not be right, it might be the "last number created" - 0 for an empty project)
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs