Skip to main content

Check that a fix resolved an incident

When Jaah files a task to fix a production incident, the incident's own page shows whether the fix worked: when the problem stopped, whether it came back, and whether the fix is credited to the task that shipped it. This guide starts from the incident. How an incident becomes a task is in How Production QA works.

Before you start: Production QA is a plan feature. While your plan does not include it, Incidents is left out of the side menu and opening the page shows Not on your plan.

Who can do this: anyone who can view the project.

  1. Select Incidents in the side menu.
  2. Pick the Project, and set State to Resolved. To see one that came back instead, set it to Reopened. Select the incident's title to open it.
  3. Read the state beside the title. Resolved means it has stopped; Reopened means it stopped and then happened again.
  4. On Overview, compare Last seen, the last time it happened, with Resolved, the time it stopped. A Resolved field shows only while the incident is resolved.
  5. Select the Tasks tab. Each task filed for the incident sits under its role, Triage, Fix or Revert, with when it was filed. Select its number to open the task and read what it changed, as in Read a task's result.
  6. Select the History tab. Events are newest first, each with its time: Resolved marks when it stopped, and a Reopened above it means it came back.
  7. Select the Ledger tab. Resolved by fix next to a task means its pull request shipped in a production release before the incident stopped, so the fix is credited to that task. It reads Pending until it is counted, then Applied.

No Resolved by fix row means no fix or triage task's pull request had shipped to production before the incident stopped: it may have stopped on its own, or another change ended it. If the incident is Reopened, go back to the Suspects tab and follow Find the pull request behind an incident.

The page refreshes every 15 seconds, so a resolve shows without a reload.