Just as a project can have many different types of work, Jira uses different issue types to help identify, categorize, and report on your team’s work. We’ll cover Jira’s standard issue types below.
The standard issue types in Jira are story, task, bug, subtask, and epic. How do they relate to each other, and how are they used? Let’s put it into context with an example. Say we’re on a team of game developers, and we’re working on the latest AAA title.
A story (or user story) is a feature or requirement from the user’s perspective. Stories should be defined using non-technical language so anyone involved in the project can understand. For example:
The player is the user of the game, and in this story, the support for an input device is required. To solve this issue, it may be necessary to assign several smaller work items to individual teammates as subtasks.
Tasks are work items that are not directly related to a user requirement but still must be completed, like the upgrading of a server, the coding of a function, or even the ordering of a pizza for the team. A task contains a more detailed and technical description of the particular work item.
In this case the task involves updating a core function of the game rather than a user feature. While tasks can generally be completed by one team member, they may also be broken down into individually manageable subtasks.
O, the lamented bug. By classifying bugs as their own issue type, we can differentiate the work they require from other issues. This enables the team do things like filter by bugs in the backlog or draft reports on the number of bugs fixed per week.
A subtask is the child of another issue, and is used to break down stories, tasks, or bugs into individually manageable pieces of work. Since they are written for the person working on the task, subtasks can be more technical than their parent issues.
In the above story of adding support for an input device, the following subtasks may be completed by different team members:
A subtask can only be created under a parent issue. However, each subtask has its own issue key and can be moved through boards independently.
Finally, an epic is a parent issue that groups stories, tasks, and bugs together to capture a large, holistic body of work. As the name implies, epics usually represent a significant deliverable. In the backlog, you can filter by issues belonging to a single epic.
In this example, the epic encompasses the story of adding joystick support, as well other stories, tasks, and bugs in an overall initiative. It might look something like this:
Subtask: [Software Engineer] Update game code
Did you get all that? Outstanding. Now let’s put your knowledge of issue types to the test. Match each of these issues to one of the 5 issue types:
Answers: (1-Epic, 2-Bug, 3-Story, 4-Task, 5-Subtask)