Triage¶
Triage is how your team decides what each failure signature is, who owns it, and when it's done. Every signature carries a triage status, an optional assignee, labels, a linked bug, watchers, a discussion and a timeline. This page explains the lifecycle: the statuses, which moves are allowed, who can make them, and the few moves DV Forge makes on its own. After reading it you'll know what each status means and why a change you tried was refused.
The lifecycle at a glance¶
stateDiagram-v2
state "Open (untriaged, investigating, root_caused, tracked, regressed)" as Open
[*] --> Open : new signature, untriaged
Open --> resolved
Open --> not_a_bug
Open --> muted
Open --> waived : admins
resolved --> Open : reopen, or a new hit (regressed)
not_a_bug --> Open : reopen
muted --> Open : reopen, or the mute ends
waived --> Open : reopen, or it expires
The five open statuses are the work in progress. You can move a signature
from any open status to any other open status (except regressed), or to any
of the closing and parking statuses. New signatures start as untriaged.
Statuses¶
| Status | Shown as | What it means | Who or what sets it |
|---|---|---|---|
untriaged |
Untriaged | Nobody has looked at it yet. | DV Forge, when a signature first appears. A person or rule reopening it. DV Forge, when a mute or waiver ends. |
investigating |
Investigating | Someone is working out what's wrong. | A person or a rule. |
root_caused |
Root-caused | The cause is known. | A person (for example with Confirm root cause after a root-cause run) or a rule. |
tracked |
Tracked | A bug in your tracker covers it. | A person, with a bug reference. Linking a bug to an open signature also moves it here, whether a person or a rule links it. |
resolved |
Resolved | Fixed. A hit after the fix reopens it as regressed. | A person or a rule. |
regressed |
Regressed | Hit again after it was resolved. | Only DV Forge. Nobody can choose it. |
muted |
Muted | Parked for now, optionally until a set time. | A person or a rule. |
not_a_bug |
Not a bug | Expected behavior or a test artifact. | A person or a rule. |
waived |
Waived | Accepted for now, with a recorded reason and approver, optionally until a set time. | A person with the project_admin role. Never a rule. |
Rules for moving between statuses¶
Open statuses move freely. From untriaged, investigating,
root_caused, tracked or regressed you can pick any other status, except
regressed. Only DV Forge sets regressed.
Closed and parked statuses reopen.
resolvedreopens tountriagedorinvestigating.not_a_bug,mutedandwaivedreopen tountriaged.
Some statuses ask for more.
- Tracked needs a bug reference: a key such as
HW-1234or a URL, up to 512 characters. Give it when you change the status, or link the bug first. While a signature is tracked you can't remove its bug link. - Waived needs a reason (up to 2,000 characters) and the project_admin role. It can take an expiry time. Rules can't waive, because a waiver needs a person to approve it. The approver is recorded on the signature.
- Muted takes an optional end time. Without one, the signature stays muted until someone reopens it.
- Not a bug takes an optional note, recorded in the timeline.
Any status change can carry a reason; DV Forge records it in the signature's activity timeline. An end time must be in the future.
Setting the status a signature already has changes nothing and isn't an error.
Merged signatures
When a signature has been merged into another, triage happens on the surviving signature. Changes to a merged signature are refused. See Merge, split and suggestions.
What DV Forge does on its own¶
DV Forge changes a signature's status by itself in exactly two cases.
A resolved signature is hit again. When a regression that ran after the
signature was resolved hits it, the signature moves to regressed. Its
assignee and everyone watching it get a notification. The comparison uses the
regression's own start time, not the upload time, so a late upload of an older
regression doesn't reopen a fix.
A mute or waiver runs out. When a mute's end time or a waiver's expiry
passes, the signature returns to untriaged and reappears in the open queue.
The timeline shows the change as made by the system.
A finished root-cause run does not change the status. The signature shows
Root-cause hypothesis ready, and a person reviews the run and selects
Confirm root cause to move it to root_caused. If your team wants this to
happen automatically, write a triage rule on "A root-cause run
finishes with a hypothesis".
Closure¶
The Closure figure on the Triage page is:
Live signatures are those that aren't merged into another and still have at
least one hit. muted doesn't count as done: a mute only postpones the work.
Who can do what¶
| Action | Role needed |
|---|---|
| See signatures, triage state and timelines | viewer |
| Watch a signature | viewer |
| Comment, attach files, save searches | member |
| Change status (except waive), assign, add or remove labels, create labels, link bugs, bulk actions, write rules | triager |
| Waive, or change a waiver's reason or expiry | project_admin |
| Write a rule that runs the root-cause agent | project_admin |
| Delete someone else's comment or attachment | project_admin |
Roles include the ones below them. See Permissions and Projects, roles and tokens.