Adapted from Atlassian Documentation that can be found here.
| Issue Type | Description | Example |
|---|---|---|
| Epic | Parent issue that groups stories, tasks, and bugs together to capture a large, holistic body of work. They represent a significant deliverable. |
|
| Story | A feature or requirement from the user's perspective. Should be defined using non-technical language. | As a player, I want to use a joystick to control my character |
| Task | Work items that implement support for the user requirement, such as upgrading of a server or coding of a function. Should contain a detailed and technical description of the particular work item. | Reduce server calls and move processing to client side |
| Bug | Issues discovered within features in the system | Character sometimes moves backward when pushing the joystick forward |
| Subtask (Optional) | An optional issue type. A child of another issue. Used to break down stories, tasks, or bugs into individually manageable pieces of work. These are written for the person working on the task and can be more technical than their parent issues. | Determine mappings that cause movement issues |
