Skip to main content

Triage

Overview​

Triage is the central place for a new request. It receives an issue from a source outside your team: a GitHub issue, an email, a tool that monitors your system, or an agent that files work through the API. No issue enters the backlog of a team before a person reviews it.

Use triage for this work​

  • A request from outside. A request for a feature, or a report of a fault, comes to you by email or through an integration. Each one arrives in the same place, and not in many different inboxes.
  • An open-source project. You manage a new GitHub issue together with the other requests.
  • Work from an agent. An agent creates an issue through the API. Triage sends that issue to a person, who reviews the work before the team accepts it.

The benefits​

  • One inbox. Every new request comes into one place for each team.
  • A review before the commitment. No request enters the workflow of the team before a person accepts it. The backlog therefore holds only the work that the team wants.

How to review a triage issue​

  • Read and assess. Read the issues in the queue, one after the other.
  • Then make a decision:
    • Decline a request that is not relevant or not valid.
    • Accept a valid request. Then set its status, for example "Todo" or "In Progress". Also set the other properties, such as the assignee and the priority.