Issues which require writing documentation for the team or end users

Issues which primarily contain or require a discussion rather than a task

Issues related to the Digital Pooling service

Issues which require active software or infrastructure-as-code development work

Issue relates to developer tooling or documentation

Issues which cannot be addressed without some design work being carried out

Issues which need deployment to the UAT environment

Issues that need manual deployment to the Staging environment

Issues that need manual deployment to the Regression environment

Issues which need deployment to the Production environment

Issues which need deployment to the Integration environment

Issues that need manual deployment to the Development environment

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

Communication required to release feature

Issues where the work required is "straightforward" (such as fixing typos, manually configuring a service), usually time-boxed to half-a-day