After a recent attempt in creating a JIRA’s plan, the following is my understanding behind the philosophy of JIRA’s epic, stories, tasks and sub-tasks. Is my understanding correct?
-
Epic (Level 1) – It is a collection of stories (aka user stories) – This is the highest level.
-
Story / Task (Level 0) – Both are at the same level. Story is for user requirement (mostly non-technical) whereas Task is for non-user requirements / implicit requirements. Ex – Database setup, Config creation for an application etc.
-
Sub-task (Level -1) – A story or a task can be split into multiple sub-tasks (mostly technical). Though the name suggests this is directly related to a task but this is common to both story as well as task. This does not exist on its own but needs a parent (story / task) issue. This cannot be linked to an epic.
Most important thing is this is not an issue type, that’s why this is not listed in the issue type drop down in a ticket.
A JIRA plan is based on above hierarchy (Level 1 -> Level 0 -> Level -1)
The following reddit thread also summarizes the same thing
https://www.reddit.com/r/jira/comments/s9jx09/comment/htqyw35/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button