Engineering writing on Jira flow analytics — what the standard time-in-status report gets wrong, and the architectural alternative we built BottleneckIQ on.
· 12-minute read
Most Jira flow plugins compute metrics from current_status plus timestamps instead of replaying the issue changelog. Six mechanisms by which the numbers drift silently — including weekends, holidays, and external waits attributed to the team. The audit you can run in 15 minutes, and the architectural alternative.
· 4-minute read
Calendar drift and external-wait drift — two business-context failures in flow analytics that distort the bottleneck signal toward stages the team doesn't control. Two 60-second checks, both fixable.
· 4-minute read
Edit-and-toggle drift — wrong-click reversals and fast-succession transitions invisible to plugins that read last-changed instead of the changelog. Two 60-second checks, one architectural fix.
· 4-minute read
Status renames and workflow restructures silently change the meaning of your historical cycle-time numbers. Two 60-second checks for workflow drift, the architectural difference between joining on name vs. ID.
