Latest from the blog
Field notes on Jira governance, configuration drift, and what an event stream can tell you that a status board cannot.
DORAoperational resilienceJiraWhat DORA Really Asks of Your Approvals
DORA no longer asks whether an approval control exists, but whether it still works across your whole Jira over time. That drift never shows in a single ticket. Here is where Article 9 fits, and why the evidence you need is already in your Jira history.
2026-08-19
JiraJira governanceworkflow governanceThe color decides, not the number
Four teams estimate in four different units, and one dashboard turns them into a single colour. When the bar is green, nobody asks what the number underneath actually means. The gap this opens up only matters when someone asks what a decision was based on. And that is where the configuration and the event history start to disagree.
2026-08-17
JiraAtlassianJira GovernanceWhy workflow bypass is one of the most invisible governance risks in a large Jira estate
Your Jira dashboards reward speed. A skipped review can look exactly like speed. Workflow bypass rarely appears as an obvious governance failure. It starts with small, defensible decisions: a review skipped, a workflow step routed around, a ticket reopened, or an issue left stuck in a status. Individually, none looks alarming. Over time, they form patterns that traditional velocity and project dashboards can completely miss. The data is already there in Jira. The real challenge is seeing the pattern early enough to act. The Bypass Risk Score turns those workflow events into a continuously updated signal, helping admins identify where governance attention is needed before a small bypass becomes a structural problem.
2026-08-14
