Skip to main content

Production QA

Production QA follows your work after it merges. It records each release of a project and each incident your monitoring reports, points to the pull requests most likely behind an incident, and, for a project that opts in, files a task to fix it or revert the change. Each release has its own page, opened from a project's pipeline on the Tasks page, and the Incidents page lists incidents for the projects you can see. It is included on some plans only.

Where Production QA fits​

Recording runs for every connected project; acting (filing tasks, reverts and probes) needs the project's Production QA switch on. Monitoring alerts arrive through an automation source, and a fix or revert is an ordinary task whose pull request goes through review and the merge lane like any other. What happens after a merge also feeds the command center's quality figures.

A release moves through Queued and Releasing to Succeeded, Failed, Cancelled or Skipped. An incident is Open when first seen, Resolved when it stops and Reopened if it returns; each repeat raises its count instead of adding a row.

Pages in this section​