This page covers what a Jira ticket should contain in it. This represents the information that developers and QA need to understand the task.
See also Scrum in Jira & Confluence
Details Required Before Development
|
Information |
Jira Field |
Applies to |
Mandatory? |
Description |
|---|---|---|---|---|
|
Project |
Project |
All |
Mandatory, Jira Enforced |
Which project is the task related to |
|
Type |
Type |
All |
Mandatory, Jira Enforced |
Is this a bug, improvement, story, etc. |
|
Priority |
Priority |
All |
Mandatory, Jira Enforced |
Highest: This ticket is blocking other functionality / Causing Major Problems / Client P1 High: This ticket is causes a function to not function as required. / Client P2 Medium: Normal priority ticket. / Client P3 Low: Feature / Problem can be worked around, doesn’t cause a major problem / Client P4 Lowest: Problem is cosmetic. |
|
Labels |
Labels |
All |
Optional |
Labels to help with filtering. Often client name, or other grouping to help with finding tickets. |
|
Summary |
Summary |
All |
Mandatory, Jira Enforced |
In one line describe the work that needs to be done. Bugs should be described in terms of what is wrong (e.g. Error when xx); improvements, stories etc should be described in terms of the desired behaviour (e.g. Quick Transfer Function). |
|
Story |
Description |
Stories, Features, Improvements |
Mandatory |
As a xx, I want yy, so that zz
|
|
Feature Description |
Description |
Stories, Features |
Mandatory |
Description of the desired outcome with as much details as possible. |
|
Screens |
Description / Attachments |
All |
Highly Recommended |
Bugs: A screenshot or video of the bug happening (e.g. error message, crash, etc). Can be marked up (e.g. notes drawn on) Improvements: A screenshot of the existing page to be improved. Ideally marked up with notes. Stories / Features: Figma designs of the desired screens. |
|
Acceptance Criteria |
Description |
Stories, Features, Improvements |
Mandatory |
A list of outcomes at the end of the ticket. Should cover normal cases and edge cases. E.g. “When a user enters text, the button becomes enabled” |
|
Bug Description |
Description |
Bugs |
Mandatory |
A description of the bug. E.g. “User gets this error when they do this, so it means they can’t do this”. |
|
Steps |
Description |
Bugs |
Mandatory |
Numbered list of the steps required to reproduce the bug |
|
Expected Outcome |
Description |
Bugs |
Mandatory |
What the user expects to happen if the steps are followed |
|
Actual Outcome |
Description |
Bugs |
Mandatory |
What actually happened when the user followed the steps |
|
Fix Version |
Fix Version |
All |
Optional |
The version that this ticket is targeted for |
|
Squad |
Squad |
All |
Mandatory |
The squad that this ticket is going to be worked on by |
|
Sprint |
Sprint |
All |
Mandatory |
The sprint that the ticket is going to be worked on in |
|
Epic |
Epic |
All |
Optional |
Link to the overarching Epic ticket that links multiple tickets for a related feature together. |