Skip to main content

Find out why an incident has no task

Jaah records every incident, but files a task for one only when the project acts on its incidents. When an incident you expected Jaah to pick up has no task, its Tasks tab is where to start. This guide reads it and points to the setting that is missing. How recording and acting differ 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 can read the tab. Changing what the project files needs permission to edit the project, and its automations are for Org Admins.

  1. Select Incidents in the side menu, pick the Project, and select the incident's title.
  2. Select the Tasks tab.
  3. Read what it shows:
    • A task under Triage, Fix or Revert, with when it was filed: a task exists. Select its number to open it.
    • Filing in place of a task number: Jaah is creating the task now. Wait a moment; the page refreshes every 15 seconds.
    • released and a time after a task: that task no longer holds the incident, so a later occurrence can file a new one.
    • No tasks filed: no task was filed. Go on.
  4. On a Regression incident, read the line under No tasks filed. It shows when the project asks for reverts but none was filed, and says why: no automation that hears the project's regressions, or no suspect pull request to revert. Adding the culprit on the Suspects tab later, as in Find the pull request behind an incident, files no revert, so start one by hand.
  5. Check the project acts on incidents. If it doesn't, Jaah records the incident and files nothing. Switch it on and add its automations as in Turn on Production QA for a project. An automation that hears incidents can also leave one out by its type, environment or severity, or hold it until its quiet hours end.
  6. Check History for when the incident was Opened. A task is filed as an incident happens, so one recorded before the project acted on incidents gets a task only if it happens again.
  7. If you need a task now, start a task for the fix yourself.

Jaah files at most one open fix task per incident, so a repeat of the same problem raises its Count but adds no second task while the first is open.