Work derived from past incidents (e.g. degradation of service) that aims to help avoid future incidents. This can be both symptom/short term geared, like improving SQL queries efficiency of an API call or root cause/long term geared, like reporting SQL queries stats or load tests.

Issue has been picked up by a reviewer, and is currently being reviewed.

To distinguish documentation that needs to be done by developers from documentation done by a supporting function

Issues which are of benefit to multiple teams but the direct responsibility of none. All teams should consider these issues in sprint planning.

Issues which have been refined and are ready to be worked on

Issues that should only be picked up when all other actionable issues in the sprint are complete

To flag draft issues that have not been completed yet

Tickets transferred from the UIS Jira Cloud instance.

Tickets assigned to the HR Systems team.

More information is needed before the issue can be refined

Dashboard issues are used to display information regarding multiple projects. They are intended to be regularly updated via a bot or other automation.

To flag issues suitable for a day blitz

Issue relates to developer tooling or documentation

To capture anticipated work while allowing it to be filtered out of epic lists/boards