Labels

Work that can be classified as change, e.g. new feature development or development of a new service.

Work that is related to a "run" activity - e.g. related to continuous running of a service, e.g. annual processes, bug fixes, support requests, framework upgrades.

Temporary label prior to identity/auth split when these will be moved to team::Authentication

Issues which ask questions about an existing business process or which require the development of a new one

Issues where the work required is "straightforward" (such as fixing typos, manually configuring a service), usually time-boxed to half-a-day. For frequently repeated automatable work, use `toil`.

This label is used for tickets tagged with team::Wilson, team::Clarke and team::Identity. It's needed for joint planning boards while the teams are combined.

Communication required to release feature

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 cannot be addressed without some design work being carried out

Issue relates to developer tooling or documentation

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

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

Issues which require writing documentation for the team or end users

The most detailed type of epic - issues are attached to epics at this level

Mid-level epic

Used for grouping detailed epics for easier management

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

Epic to be used as a container for other epics related to a specific product