Specify JIRA subtask ID

I'd like to specify (part of) the subtask ID. Using JIRA for bug tracking and sometimes a bug must be fixed on multiple branches. I'd like to use subtasks to specify the different branches. Unfortunately, our developers can get confused by different issue IDs so I'd like have subtasks inherit the parents' ID. Something like parent ID is 5000, subtask 1 is 5000.1, subtask 2 is 5000.2.

Is there a way to achieve this?

4 answers

1 accepted

This widget could not be displayed.

No. Sorry.

Jira issue keys are generated sequentially within the project. You can't change it without a massive rewrite of core code.

A number of sites I know of have assorted work-arounds. One I coded was a simple derived field that displays the parent and child numbers together (it's aimed mainly at sort on the navigator). I've also seen auto-sequencing done, but that felt a little clunky to me. All the solutions I've seen are separate from the key as Jira sees it though.

That's unfortunate. I noticed JIRA filters often display the parent ID before the subtask ID which helps the context, but for a developer that's doing a smart commit that context won't exist on the CLI. Thanks anyway, though.

This widget could not be displayed.

Same issue. Trying to organize Project Portfolio Office. I think PPO functionality would be a great improvement for JIRA.

This widget could not be displayed.

This is exactly what I'd like to do.  Our issues tend to represent scrum sprints or epics within a project more than individual issues such as bugs or service requests.  This is not always the case but it's pretty common.   The problem with creating a sub-task at the same numbering tier is that things get cluttered easily.  In my opinion,  there needs to be a new structured tier under an issue to handle this scenario.  This is what I expected from sub-task,  not a linked peer issue but a lower level task.

Right now I using keywords like STATUS: at the top of comments for these which is a kludge.

This widget could not be displayed.

yes please.  seems like a basic way of structuring sub tasks but kind of annoying that in my "Open Issue" list when I sort I might get new sub tasks listed in between primary tasks.  I have a filter for main tasks that helps.

Same answer - it's not going to happen.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

265 views 1 3
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you