Skip to content
Sign inRequest access

Status lifecycle

Every report carries exactly one status: the single field that says where it sits in your team’s flow, from the moment it lands to the moment it is closed out. The set is small and fixed on purpose, so a status means the same thing to everyone in the account.

The stored values are exact: the inbox, the filters, the board columns and the API all use these strings.

new

Freshly captured, nobody has looked at it. Every report starts here the moment it is ingested.

in_progress

Somebody has picked it up: investigating, reproducing, or fixing.

waiting

Blocked on somebody else. You have asked the reporter a question, or you are waiting on a third party. It is not abandoned, and it is not being worked on either.

resolved

Handled: fixed, answered, or otherwise dealt with.

archived

Set aside: noise, a duplicate, or work you have chosen not to do. Archived reports stay fully viewable; they are simply out of the active flow.

The set is fixed. You cannot add, rename or remove a status, and there are no custom workflows. That is what keeps a column on the board meaning the same thing across every project and every member.

Any status can move to any other, directly: new straight to resolved, resolved back to in_progress, archived back to new. On every route a person drives — the report page, a board drag, a bulk action, the REST API — the server validates that the target is one of the five and checks nothing else about the move.

One server path does look at where the report is coming from, and it is not a person: a tracker webhook will never move a report out of archived. See the tracker tab below.

  1. Open the report. See the report page.
  2. Pick the new status in the Triage card.
  3. It saves the moment you pick it, and you get a confirmation.

Changing a status is its own permission, so a role can be allowed to read the inbox without being able to move work through it. A member only ever sees and moves reports inside their own account, their granted spaces, and the projects they can reach.

A status change made on a single report is written to the audit log as feedback.status_changed, carrying the report, the timestamp, and the move itself as from and to. All four single-report routes write it: the dropdown, a board drag, the REST API, and the tracker webhook.

Who the row names depends on which of those it was. The dropdown and a board drag name the member who made the change. The REST API names the key rather than a person — an account holds several, and after an unexplained change the useful question is which one to revoke. A tracker webhook names nobody at all: nothing signs in to fire it, so the row records the tracker and the issue it came from instead.

A bulk action is recorded differently. It writes one row, feedback.bulk, naming the action and how many reports were applied and how many skipped — not which reports moved, and not what they moved from. So a bulk close leaves a record of the batch, and no per-report trail.

These rows are filed as activity rather than compliance, and that sets how long they are kept: 30 days by default, where compliance events — role and invite changes, plan and billing, suspension and deletion — are kept a year. Capture and retention are platform settings rather than per-account ones: you do not configure this, and you cannot switch it off for your own account either. There is no audit screen inside your workspace; the rows travel in your account data export.

A status change only notifies when the value actually changed. Setting a report to the status it already has is a no-op and tells nobody.

Moving to resolved is treated as its own event, distinct from any other move. Every route to it surfaces as resolved: the dropdown, a board drag, a bulk action, the REST API, the tracker webhook. So a channel or a member subscribed to it hears about the close no matter who or what did it. Every other move is a plain status_change.

Who hears about it, and over which channel, follows each member’s preferences and the project’s channels.

  • Two people at once. Last write wins: there is no lock and no conflict warning, so the later write is simply the one that sticks. The audit log records both moves, in order — not the winner alone, which is how you can see afterwards that there were two.
  • Older than your plan’s history window. The report is outside the window, so status changes are refused on it: from the report page, from a bulk action, and from the API alike. It is hidden, not deleted.