which issue comes first and which issuetype comes after. For example, STORY is child of EPIC, but where does this TESTPLAN sits ?
Hi @Amit Mishra,
It depends on how the TESTPLAN issue type (work type) is configured in your Jira:
If TESTPLAN is a standard issue type (not a sub-task), it sits at the same hierarchy level as Story/Task/Bug (level 0) – typically a child of Epic and parent of Sub-tasks.
If TESTPLAN is configured as a sub-task issue type, it will sit under Story/Task/Bug (level -1).
You can verify (and change, if you’re an admin) where it sits in the hierarchy here in Jira Cloud:
Settings → Work items → Work type hierarchy (read the docs here)
Hope it helps 🙌
Hello @Amit Mishra
In Jira Cloud, the default hierarchy is:
Epic = level 1
Story / Task / Bug and other standard issue types = level 0
Sub-task issue types = level -1
Also, when a new issue type is created, Jira adds it either as standard or sub-task. A standard issue type starts at the story level unless an admin explicitly maps it to a higher level in Work type hierarchy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey folks,
To quickly chime in here, here's a nice official resource related to DevOps process and managing tests in Jira: How to create and manage test cases with Xray and Jira 📚
It does reference Xray, but a similar concept can be used with other third-party tools, or if you're going to create a workaround with native functionalities. 👀
To also add on previous replies, what I've seen mainly in implementations, the Test Plan tends to sit on level 0 in the hierarchy.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.