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

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

HR Integration Application

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.