Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

For the key in the issue, can I manually set the key for each issue?

For the key in each issue, currently it is a prefix + an auto increment number in JIRA work management, such as "ABCD-101". In my use case, we would like to distinguish the task hierarchy in the key and set the sequence number according the sequence of the event actual happen. 

Here is an example.

ABCD-1 Organize a meeting

ABCD-1-1 Book a room

ABCD-1-2 Send out an agenda

ABCD-1-3 Provide meeting material

ABCD-1-3-1 Prepare product factsheet

Is it possible to do it in JIRA? Any alternative?


2 answers

Welcome to the Atlassian Community!

No.  Jira has an issue naming scheme that you can not change, it's always <project key>-<sequence>

All you can do for your scheme is create issues and sub-tasks in the right order, so that they take on a sequence that matches your desired order.

But, relying on the issue key to sequence things is completely the wrong approach, you should be looking at useful ways to sequence your issues.

0 votes
Curt Holley Community Leader Jun 06, 2022

Hi @hkstreetname 
Welcome to the Community!

It is not possible to mess with the key numbering in Jira.

But you can use a (let's say "Dependency") link type to show which task is prerequisite to another. You could add the sequence number to the beginning of the Summary to impersonate what you propose above, just not all in the key.

You can even automate all of this (if it is a repeatable sequence) See example below, Where you have the sub-tasks in order and link them via the "most recently created issue".Screenshot 2022-06-07 155206.png 

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events