Control Coverage Rate(5.7.6)

Control coverage asks two questions of every resolved issue. Was a worklog recorded on it? And was it resolved without ever jumping from a To Do status straight to a Done status in a single step? The control coverage rate is the percentage of a project's resolutions for which both answers are yes. It describes what Jira recorded for each resolution, not the quality of the work behind it.

What you can conclude

• A project with 88% coverage means 12% of its resolutions missed at least one of the two checks.
• A project far below the others, for example 60% against a portfolio mostly above 90%, is where a reviewer could ask which check its resolutions miss and whether that is expected for the kind of work it does.
• A project near 100% passes both checks on almost every resolution; the checks say nothing about what the worklogs contain.
• Each bar covers every week in the selected range, including the week in progress. The Avg control coverage card above reads the latest complete week on its own, so the two can legitimately disagree.

How this chart works

Horizontal bar chart showing, for each project, the percentage of resolved issues that passed both checks (green) and the percentage that missed at least one (red). Statuses are judged by their Jira status category, and a resolution misses the worklog check when no worklog was recorded on the issue at any point. The Avg control coverage card above colors its value green at 95% or more, amber from 80% to 94% and red below 80%. Use the date and project filters to focus on specific teams or periods.