Skip to content

Working a signature

Each signature's page has a Triage card where you set its status, owner, labels, bug and watchers, plus Discussion, Attachments, Activity and Rule runs sections. This page walks through each of them, what they need, and who can use them. Open a signature from the triage queue or the Signatures page.

Change the status

The Move to… menu next to the status badge lists only the moves the lifecycle allows from the current status. Hover an option for a one-line description.

Most moves apply at once. These ask for more in a dialog first:

Moving to The dialog asks for
Tracked Bug: a key or URL (required unless a bug is already linked).
Waived Why is this acceptable? (required), and optionally The waiver expires On a date and time. Only project_admin and org_admin see this option.
Muted An optional Note, and optionally Unmute automatically On a date and time.
Not a bug An optional Note.

Times are in your local time and must be in the future. When the time comes the signature returns to Untriaged.

Under the status you'll see when it last changed and by whom: a person, a rule, or the system (a new hit, or a mute or waiver running out). A waived signature shows its reason, approver and expiry. A muted one shows when the mute ends, or that it stays muted until someone reopens it.

Changing status needs the triager role; waiving needs project_admin.

Confirm a root-cause hypothesis

When a root-cause run launched on this signature finishes, the status doesn't change. Instead the card shows Root-cause hypothesis ready with a Review the run → link. After reviewing it, select Confirm root cause to move the signature to Root-caused. The banner appears while the signature is open and not already root-caused. See Runs and hypotheses.

Assign an owner

Pick a member in the Assignee menu, or select Assign to me. Choose Unassigned to clear it. The list shows the members of the project's organization.

When you assign someone:

  • they start watching the signature, and
  • they get a notification, unless they assigned themselves.

Assigning needs the triager role. Someone who has left the organization still shows as the assignee until you change it, but can't be newly assigned.

Add labels

Labels are project-wide tags. Every signature in the project draws on the same set, so a label means the same thing in filters, rules and exports.

  • Add label… adds an existing label.
  • New label creates one inline: type a name (up to 64 characters), pick a color, and select Create. The new label is added to this signature.
  • Select the × on a label to remove it.

Label names are unique within a project, ignoring case. Managing labels needs the triager role.

Filters and rules refer to labels by id, so renaming a label keeps every saved filter and rule working. Renaming and deleting labels is available through the API today:

# Rename
curl -s -X PATCH "https://api.daruur.cloud/v1/labels/$LABEL_ID" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"name": "infra-license"}'

# Delete: removes it from every signature; rules that add it skip from then on
curl -s -X DELETE "https://api.daruur.cloud/v1/labels/$LABEL_ID" \
  -H "Authorization: Bearer $TOKEN"

The Bug row holds one reference: a tracker key such as HW-1234, or a URL (up to 512 characters). URLs open in a new tab.

  1. Select the pencil next to Bug.
  2. Enter the key or URL and select Save.

Linking a bug to an open signature moves it to Tracked (the editor says Saving moves it to Tracked). On a resolved, not-a-bug, muted or waived signature the bug is recorded and the status stays as it is.

Remove link clears the bug. It isn't offered while the signature is Tracked, because Tracked needs its bug: move the signature to another status first. Linking needs the triager role.

Watch the signature

Select Watch to follow a signature, or Stop watching. The row also shows who else is watching.

Watchers hear about regressions and rule notifications; see Notifications. You start watching automatically when you're assigned or when you comment. Any role can watch.

Discussion

The Discussion section holds comments for whoever picks the signature up next.

  • Type in Add a comment… and select Comment (or press Ctrl+Enter). Comments can be up to 20,000 characters.
  • Commenting subscribes you: you start watching the signature.
  • You can edit your own comments; edited comments show edited.
  • The author or a project admin can delete a comment.

Commenting needs the member role. API tokens can't comment.

Attachments

Attach evidence to a signature: logs, archives, documents, screenshots, waveform captures.

  1. Select Attach file and choose a file.
  2. It uploads and appears in the list.

  3. Any file type is accepted, up to 10 MB per file. Empty files are refused.

  4. Images get thumbnails; select one to view it larger. Other files download.
  5. A file that claims to be an image (PNG, JPEG, GIF, WebP) or a PDF must really be one, or the upload is refused.
  6. Files a browser could run or render as a page (HTML, SVG, XML, JavaScript) are stored as plain downloads and never open in the browser.
  7. The uploader or a project admin can delete an attachment. It's removed for everyone.

Uploading needs the member role. API tokens can't upload attachments.

Activity timeline

The Activity section lists everything that happened to the signature, newest first, with who did it:

  • sightings: first seen, hit again, came back after an absence, regressed (each links to its regression);
  • status changes, with the bug, end time or reason given;
  • assignments, labels added and removed, bugs linked, classification changes;
  • comments and attachments;
  • root-cause hypotheses ready and runs that failed;
  • merges, unmerges and splits.

Actors include people, rules (shown as Rule "name"), API tokens, the root-cause agent, re-bucketing, and the system. Select Load older to page back. The timeline updates live as changes happen.

Rule runs

When triage rules have matched the signature, a Rule runs section shows the latest 20 matches: when, which trigger, and each action's outcome (applied, skipped with the reason, or failed). See Triage rules.

Change a mute or waiver

A mute or waiver can be changed while it's in effect, through the API today. Send the same status again with the new terms:

curl -s -X POST "https://api.daruur.cloud/v1/signatures/$SIG_ID/status" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"status": "muted", "until": "2026-12-15T09:00:00Z"}'
curl -s -X POST "https://api.daruur.cloud/v1/signatures/$SIG_ID/status" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"status": "waived", "reason": "Known erratum, fix in B1 silicon", "until": "2027-03-31T00:00:00Z"}'
  • A mute takes a new end time (it doesn't take a reason).
  • A waiver takes a new reason, a new expiry, or both. It needs the project_admin role, and you become the recorded approver.
  • The new time must be in the future.

To end a mute or waiver early, reopen the signature to Untriaged.