Direct Open-to-Done Skip(5.2.7)

A ticket that transitions directly from "To Do" to "Done" in a single step bypassed every intermediate stage: In Progress, In Review, testing, verification. Sometimes this is legitimate — a task determined to be unnecessary. When it happens frequently, the question is whether the work and its review happened outside the recorded workflow, or whether the workflow's stages no longer match how the team works.

What you can conclude

• A high count of direct open-to-done transitions means many delivered tickets skipped every intermediate stage; a reviewer could ask whether the workflow's stages still match how the team works.
• A spike in a specific week often lines up with a sprint end.
• A declining count means fewer delivered tickets are skipping the intermediate stages.

How this chart works

Weekly bar chart showing issues closed directly from an initial open state to a delivered terminal state, bypassing all intermediate stages, shown as an absolute count per week. Each skip is also recorded by the type of account that made it (person, app, customer, unknown, erased, or system where no actor was recorded); the types add up to the count, and only people's skips are counted as people's. Skips into statuses your organization classifies as abandoned (a MetaFrazo default applies until configured) are backlog hygiene and are not counted.

The week in progress is shown at its count so far. Because the week is not yet complete, it covers only what has been recorded up to now and can only grow as the week closes. The chart counts whole weeks: a week that falls only partly inside the selected date range is left out, so the chart can show fewer weeks than the range spans, and a caption under the chart names the week that is not included. This applies at both ends of the range, apart from the week in progress.