I would like to adjust the item# sequence so things(under epics) are categorized by their number pool. Currently if I create all the initial items, then add some more, in say my first epic, the sequence continues from the last number. EXAMPLE BELOW. This problem really is more cosmetic but it can throw people off and would be much better if fixed. PLEASE help :)
Hello @Sina Abdi
Welcome to the community.
The number portion of the issue ID is assigned automatically and sequentially. JIRA keeps track of the last number used in the project and uses the next available number the next time an issue is created in the project. You cannot reserve numbers for issues.
If I have misunderstood your concern, please provide more information.
You understood the summary correctly. My question still looms though. Can you stop that from happening and or change it? Perhaps in a different project type or setting or board or something, it is a bit distracting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you make the Items follow just the epic's lead instead of sequence. For example Epic 1- tasks- 1.1,1.2,1.3,1.4 Epic 2, 2.1,2.2,2.3,2.4....
It would be helpful if you could do that, or again just get rid of the numbers somehow, or use something else.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, there is no support for manipulating how the applications assigns issue keys for any type of project/board within JIRA. And the display of the issue key in screens such as the one you pasted is fundamental to the product, so you can't remove the display of the information.
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.