checked in care · engineering

Engineering capacity

Loading the latest numbers from Jira…

—
Committed next00Status Dev Ready
In dev00IN DEV, In Review · 30 days
In QA00QA Ready, In QA · 30 days
Blocked00Updated in 30 days
Release pipeline00Awaiting CAB, SB or PROD
Closed00Last 30 days

Where work sits

Dev, QA and Blocked count items touched in the last 30 days. The release pipeline counts everything waiting, however old.

By stream

Derived per item: a V2/2.0 epic → V2 modules; the Production issues epic, or a bug with no epic → Production bugs; a named customer in Client → Customer delivery; the rest → Platform & internal.

By assignee

Current Jira assignee, including BAs and support staff who hold tickets. In flight = dev + QA + blocked.

By customer

The Client field on each ticket, as entered. Committed counts Dev Ready.

Board hygiene

These inflate any count taken from Jira status categories and hide real capacity.

Stale in-flight00Dev, QA or Blocked, untouched 30+ days
Released, not closed00Status Released to Production
Intake backlog00To Do, In Analysis

Active items

Started is when the item last changed status category (from To Do into progress); for committed items that can be the day the ticket was raised. Click a column to sort.