Skip to content

The triage queue

The Triage page is where you work through signatures as a team. It shows where the project stands, lets you build any filter and save it, and lets you act on many signatures at once. When you find yourself repeating the same bulk action, you can turn it into a rule in one step. Open it from Triage in the sidebar.

Summary cards

The top of the page summarizes the project's live signatures (not merged, with at least one hit):

Card What it shows
Open Signatures in an open status: untriaged, investigating, root-caused, tracked, plus regressed.
Closure Resolved, not a bug and waived, as a share of live signatures. See Closure.
Unassigned open Open signatures nobody owns. Select it to filter the queue to them.
Live signatures All live signatures.

Below the cards, one chip per status shows its count. Select a chip to show just that status.

The default view

With no filter in the link, the queue shows open work: signatures whose status is untriaged, investigating, root-caused, tracked or regressed, sorted by Last seen, 50 per page.

  • Open work returns to this view.
  • Everything shows every live signature, whatever its status.

The filter, sort, page and selected saved search live in the page's URL, so every view is a link you can bookmark or send to a colleague.

The table shows each signature's title (with its labels and bug), status and root-cause agent state, assignee, hits, when it was last seen, and when its status last changed. Select a title to open the signature.

Build a filter

The Filter card holds rows of conditions:

  1. Choose Match all or any of these conditions.
  2. Select Add condition. Each row has a field, an operator and a value. For example: Status · is any of · Untriaged, Regressed.
  3. Select Apply.

Pickers appear where the values are a closed set: statuses, classifications, agent states, project members, labels. Members include Me, which always means whoever is viewing. For durations type 30m, 12h, 7d or 2w. For dates use the date-time picker, in your local time. A row that isn't complete shows why under it and is left out until you fix it.

You can add up to 20 rows. If a saved search contains nested groups or a not the builder can't show as rows, they're kept as-is: you can view them as JSON or remove them, and they're saved back unchanged.

The full list of fields and operators is in the Filter language reference.

Tip

A filter the API refuses (for example an unknown value in a hand-edited link) shows Couldn't load the queue with the reason, and a button back to open work.

Saved searches

Save the current conditions under a name to reuse them.

  1. Build the filter (it doesn't need to be applied).
  2. Select Save as…, enter a Name (up to 128 characters), and optionally tick Share with the project.
  3. Select Save search.

Pick a search from the Saved search menu to load it. The menu groups Mine and Shared with the project. When you change the conditions of a search you own, it shows modified and an Update "name" button saves the new conditions. The trash button deletes a search you own.

Private search Shared search
Who sees it Only you Everyone in the project
Who can change or delete it You You, or a project admin
Can use Me Yes Yes, unless a rule scopes to it
Can scope a triage rule No Yes

Saving a search needs the member role. API tokens can't save searches.

A shared search that a rule scopes to is part of that rule:

  • It can't be unshared or deleted while a rule uses it.
  • Changing its filter needs the role it takes to write the rule: triager, or project_admin if any of those rules runs the root-cause agent.
  • Its filter can't use Me, because rules run without a signed-in user.

Note

In the app you choose whether a search is shared when you save it, and you can update or delete only your own searches. Renaming a search, changing whether it's shared, or a project admin editing someone else's shared search is available through the API (PATCH /v1/saved-searches/{id}).

Sort

Sort by offers Last seen, First seen, Hits and Status changed. Each sorts newest (or most) first. Select Apply after changing it.

Select rows and act on them

Tick the box on a row to select it, or the box in the header to select every row on the current page. The bulk toolbar above the table then acts on the selection:

Control What it does
Set status… Moves every selected signature to the status you pick.
Assign… Assigns them all to one member, or Unassign.
Add label… / Remove label… Adds or removes one label.
Watch / Unwatch Starts or stops you watching them.

Status changes that need more ask in a dialog first:

  • Tracked: a Bug reference, optional in bulk. Leave it empty to keep each signature's own bug; signatures without one don't move.
  • Waived: a reason (Why is this acceptable?) and an optional expiry. Waiving needs the project_admin role; without it the whole request is refused.
  • Muted: an optional note and an optional time to Unmute automatically.
  • Not a bug: an optional note.

Bulk actions need the triager role, except watching, which any role can do.

How many at once. The API accepts up to 200 signatures per request. The queue acts on the selected rows of the current page, so at most one page (50) at a time.

Partial success. Each signature is checked on its own against the lifecycle rules. After the action a banner reports how many were updated, how many were already that way, and how many couldn't change. Expand Why some didn't change to see each failure and its reason (for example a move the lifecycle doesn't allow, or a signature that was merged meanwhile). The signatures that failed stay selected so you can deal with them.

Make this a rule

After a bulk action a rule could repeat, the banner offers Make this a rule. It opens the rule editor prefilled with:

  • the trigger A new signature appears,
  • the queue's current conditions as the rule's conditions (minus any Me conditions, which a rule can't use),
  • the action you just took.

It's offered after setting a status, assigning someone, adding a label, or moving to Tracked with a bug (which becomes a Link bug action). It isn't offered for unassigning, removing labels, watching, or waiving, since rules can't waive. Review the rule, check the Would match count, and save it. See Triage rules.

Export CSV

Export CSV downloads the queue's whole selection, not just the current page: the same filter and sort, up to 50,000 rows. Columns:

id, signature_key, title, status, assignee, labels, bug_ref, classification,
severity, msg_id, failure_count, regression_count, recurrence_count,
first_seen_at, last_seen_at, status_changed_at

Labels are joined with ;. Times are ISO 8601. A cell that would start with =, +, -, @, a tab or a carriage return is prefixed with ', so a spreadsheet treats it as text rather than a formula.

The same export is available from the API:

curl -s -G "https://api.daruur.cloud/v1/signatures/export.csv" \
  -H "Authorization: Bearer $DVF_TOKEN" \
  --data-urlencode 'filter={"all":[{"field":"status","op":"eq","value":"regressed"}]}' \
  --data-urlencode 'sort=last_seen' \
  -o regressed.csv