nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I create multiple subtask issue types?

EduardCampo

Hello, I am used to working with Azure boards and was wondering if I could define the heriarchy of the issue types.

My goal is to have a user story contain subtasks of different types, like:
- Bug

- Task

- Analysis

- Improvement

And have a board where I can move them around always under a User Story.

If this is not possible, I would have the "epic" be my grouping and then all the tasks be under it on the board.

Accepted answers

Jack Brickey

You can certainly create different sub-task Issuetypes with different names. However, might I suggest a different approach? You could create a custom field that qualified the type of sub task. You could make it a required field when adding a Sub-task. IMO this presents a cleaner solution since traditionally the list of "subtask types you show are actually associated with "task/story" Issuetype.

All comments

Jack Brickey

EduardCampo

I have not been able to create subtype issues, only one can be created and the rest go to the standard task level without any way for me to choose which level should it be on.

You are right that a field on the subtask would be a clean solution but I would like to have custom workflows and fields for each subtask type in this scenario.

Jack Brickey

Ah...so you are likely using Team Managed Project which does not allow for this.

Company managed does as shown below. Again, using "task", "Bug", "improvement" as subtasks will get confusing when you have them as both Task level and Subtask level issuetypes (opinion).

Kelly Arrey

Hi @EduardCampo

Usual disclaimers apply, YMMV, deuces are wild, etc., but I'd recommend sticking with the out-of-the-box issue hierarchy where Stories, Bugs and Tasks all exist as standard or base issue types, not sub-issue or subtask issue types, and they can be grouped under Epics, for the following reasons:

Anyone who's ever used Jira before will be confused that bugs and tasks are now sub-issue types
You will incur some administrative overhead to set up bugs and tasks as sub-issue types
The built-in Epic issue type seems to do what you want in terms of grouping bugs and tasks, it just has a different name than Story - does the name of the issue type really make that much different to the value you're going to get out of this implementation? Is it really worth the effort to configure and maintain this change?

If you want to add custom issue types for Analysis, Improvement, etc,, I would add them as standard issue types, i.e., at the same level as Stories, Bugs, Tasks, not sub-issue types.

HTH,

Kel

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud