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?
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.
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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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