Interpret deploy coverage and investigation gaps in a weekly report
Open a retained report under the environment’s weekly report setup when the Slack summary omits a category or shows a verification gap.
Read the week’s results and identify coverage gaps#
The note leaves out the deploy, scan, existing-problem or fix pull request lines when the week recorded none. It never calls a week healthy.
A deploy counts as verified only when each of its four checks ended No regression or Regressed and established everything it reads. A check that ended Incomplete or Replaced reached no verdict, so its deploy is not counted as verified, and neither is a deploy with a change-check gap, whatever its checks found. A deploy that got no verification stays in the total. The span ends 25 hours before the week does so that all four scheduled checks for a deploy that landed are due by the end of the week. A deploy that lands on the week's last day appears in the next week's report. Read a deploy's verification explains the four checks.
The report can show Investigations, Deploys, Latent risks, Fix pull requests opened, Investigation gaps and Setup gaps. Use these sections to follow the week's work and distinguish recorded results from missing measures.
Investigation gaps covers gaps an administrator can close that opened in the seven days before the report week. It shows the share closed within 7 days, plus each gap's opening investigation and closing time, using records through the end of the report week. Older reports created before this section existed do not include it.