Made by Pixelmatters’ Product Team 💙🧡
Specially created for JIRA issues, these templates can be adapted as a standard for any type of project.
From Product Owners to Engineers and Designers, these templates will help anyone on your team always be up-to-date and find all the necessary information.
<aside> 🔍 You can find more information on creating issue types and customizing their fields on Jira in this guide.
</aside>
<aside> 💡 This goodie focuses on Jira once it's Pixelmatters' project management tool of choice. Still, these templates can be used on other project management tools, like Trello and Asana.
</aside>
To add issue types and edit them, visit your JIRA project and go to: Project Settings > Issue types
Project Settings > Issue types
Project Settings > Issue types
| Issue Type | Summary | Fields | Description |
|---|---|---|---|
| Epic |
| Epics track collections of related bugs, stories, spikes, and tasks. | -Description -Start date -End date -Labels | -Description -Milestone -Deadline | | Bug
| Bugs track problems or errors. | -Description -Assignee -QA Assignee -Labels -Sprint -Story Point Estimate | -Description -Information —OS: —Browser: —Other: -Steps to Reproduce -Expected Results -Actual Results -Evidence | | Spike
| Spikes track the investigation of a given technical doubt. | -Description -Assignee -Labels -Sprint -Story Point Estimate | -User Story -Technical Notes -Conclusion | | Story
| Stories track functionality or features expressed as user goals. | -Description -Assignee -QA Assignee -Labels -Sprint -Story Point Estimate | -User Story -Acceptance Criteria -Technical Notes -QA Notes -Resources | | Task
| Tasks track small, distinct pieces of work. | -Description -Assignee -Labels -Sprint -Story Point Estimate | -User Story -Acceptance Criteria -Technical Notes -QA Notes | | Subtask | Subtasks track small pieces of work that are part of a story. | -Description -Assignee -Labels -Sprint | -Acceptance Criteria -Technical Notes |