Workflow Adherence Score by Project(4.4.7)

A bypass here is a specific, observable thing: an issue moving straight from a new-category status into a delivered-classified terminal status, skipping every working state in between. The workflow adherence score measures what share of completions did NOT do that.

A high adherence score means completed work passed through the working states your workflow defines. A low score means completions are commonly jumping straight to done, and the working states exist on paper more than in practice.

What you can conclude

• A score above 80 indicates completions consistently pass through the defined working states.
• A declining score over time indicates straight-to-done completions are becoming more common, which is a process conversation worth having.
• A week with no adherence value had no completions to assess; that is an absence of evidence, not a bad score.

How this chart works

Per project and week: transitions into done-category statuses are counted, the share arriving from work-in-progress statuses is the adherence percentage, and the tier badge (mature / developing / at risk) reflects it. Whether a status is terminal comes from your own Jira status categories; whether reaching it counted as delivery comes from your terminal-status settings, with a MetaFrazo default reading of the status name until you configure one. Entries into statuses you count as abandoned are backlog hygiene: excluded from the score and reported alongside it in the abandoned column, and a week whose completions were all abandoned shows no score rather than a zero. Use the date and project filters to focus on specific teams or periods.