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; } } }

Issue hierarchy in a project

Martijn van Landschoot

For a new project my team would like to work with the following issue hierarchy:

Epic
|__ __Story
| |__ Sub-task
| |__ Spike
|__ Task
|_____ Sub-task
|_____ Spike

It shouldnt be possible to make an story/task without an Epic in this project. How can I configure/enforce this hierarchy in the project?

Accepted answers

For your ‘must have an epic’ requirement you could make the Epic Link field required in the Story and Task workflow via Validator.

All comments

Milan Chheda [INFOSYSTA]

First create a new issue type called 'Spike'. It should be sub-task and not start standard.
Create Epics in your Projects
Open any epic, and click on Create issue in epic (select issue type as Story or Task)
Next, open the created Story/Task and click on 'Create Sub-task'. It should give you 2 issue types (Sub-task or Spike)
That's it! Your hierarchy is created.

For your ‘must have an epic’ requirement you could make the Epic Link field required in the Story and Task workflow via Validator.

Welcome!

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

Quick Links

Find more posts tagged with

jira