Skip to content
Sign inRequest access

Saved views & bulk actions

Two things turn the inbox from a list you read into a queue you work: views your space shares, and bulk actions that apply one change to many reports.

A saved view is a named set of inbox filters, stored and shared with everyone in the space. It is not a bookmark and not a private preference: the filters in the inbox are not kept in the address bar, so saving is the only way to hand a slice of the inbox to a colleague.

  1. Filter the list to exactly the slice you want: say, new reports with no assignee on one project.

  2. Give it a name in Save the current view. You may name it in both Arabic and English, up to 80 characters.

  3. Save. It appears as a chip above the filter bar, for you and for everybody else in the space.

  4. Click the chip any time to apply it; the small × on the chip deletes it, after a confirmation that names the view.

A view stores all six filters: status, priority, project, assignee, label, and the search term.

When you need to act on many reports rather than open each one, select rows in the list and apply one action to all of them.

  1. In the list, tick the reports you want, or use the header checkbox to take every report on the current page.

  2. A bar appears with the count selected.

  3. Pick an action from the bar. It applies immediately; there is no second confirmation.

The bar offers three, and they cover the fourth:

Action What it does
Set status… Moves every selected report to new, in_progress, waiting, resolved or archived. Archiving a batch is this, with archived.
Assign to… Sets the assignee on every selected report (or clears it), and notifies each new owner.
Add label… Adds that label to every selected report, without duplicating it where it is already applied.

Everything a bulk action does is also available one report at a time from the triage panel; bulk is throughput on top, not a separate capability. Status and assignment changes fire the same notifications they would individually, and the in-app notification names who made the change — the emails do not. What a batch does not leave behind is a per-report trail: a report carries no change history you can open, so afterwards nothing on the report itself can tell you it was one of the 500, or who moved it.