From the course: Complete Guide to Jira Administration: Configuration, Management, and Automation

Unlock this course with a free trial

Join today to access over 24,800 courses taught by industry experts.

Leveraging issue hierarchy

Leveraging issue hierarchy - Jira Tutorial

From the course: Complete Guide to Jira Administration: Configuration, Management, and Automation

Start my 1-month free trial Buy for my team

Leveraging issue hierarchy

“

- [Instructor] In the last section, when creating a new issue type, you may have noticed that Jira asked for a standard issue type, which is labeled Level 0, or a sub-task issue type, which is labeled Level -1. I find the naming little confusing, so here's an explanation. I like to think of standard issue types as parents and sub-task issues as children. For example, if the parent type is task, the child type is sub-task. But sub-tasks aren't limited to only being children of tasks. A sub-task can be a child of any other issue type. For example, it's common for development teams to break up the work required to complete a story into multiple sub-tasks. In Jira Cloud, the parent level is called Level 0, and the sub-task level is called Level -1. There's one more level to know about in Jira Cloud, and that's Level 1 for epics. I think of epics as grandparents. Sticking with our family metaphor, let's talk a little bit about hierarchy and how different issue types relate to each other…

Contents