Skip to content
Sign inRequest access

Labels, priority & assignment

Assignment says who, priority says how urgently, and labels say what kind. The inbox filters on all three, and you set them from the Triage card on any report page. Every change records who made it and when.

A report is owned by exactly one teammate: single ownership, no shared assignees. Pick a member for Assignee, or leave it unassigned.

  1. Open the report and find the Triage card.

  2. Choose a teammate under Assignee; it saves the instant you pick.

  3. To hand it off, pick someone else. To drop ownership, choose Unassigned.

The dropdown only offers people who can actually reach this report’s project. A colleague confined to other projects is not listed, because a list whose entries the next request refuses is worse than a short list. Suspended members are excluded for the same reason: a card that looks like somebody’s queue and never moves is not an assignment.

Every report carries a priority on a fixed five-value scale, defaulting to none. Everywhere the dashboard shows it — the board chip, the list column, the report page, the notification bell — it is a word in your own language, never a colour alone.

Value Shown in the dashboard
urgent Urgent
high High
medium Medium
low Low
none None (default)

The priority-change email is the exception: it prints the raw value (urgent, high) rather than the word, including in the middle of an Arabic sentence. A status change in that same email is translated; the priority is not.

The scale is fixed: it cannot be renamed or reconfigured per project. On the board, a priority chip is only drawn when the value is not none: a chip on every card saying “None” costs a line of the card to say nothing.

Labels are the shared taxonomy of a space: a set like Bug, Idea, Question, Improvement defined once and available on every project inside that space. They apply to survey responses as well as reports, so one taxonomy covers both.

Every new account’s first space is seeded with those four, in both languages at once (Bug / علة, Idea / فكرة, Question / سؤال, Improvement / تحسين), so a bilingual team is not stuck with whichever language the account happened to sign up in. Rename them freely; they are ordinary labels.

Anyone whose role allows labelling can tick one or more labels on a report and save. A report can carry as many as apply. On the report page they are that tick list — every label in the space, with the applied ones ticked. They show as coloured pills on the board card (the first three, then a +N) and on the list row, and the Label filter pulls up everything carrying one.

Creating, renaming, recolouring and deleting are separate, finer permissions than applying: viewing the taxonomy, creating, updating and deleting are four distinct keys, so you can let a team label reports without letting them redefine what the labels mean. See Roles & access.

  1. Open Labels in the space. Each label shows how many reports carry it.

  2. Create one with a name (up to 50 characters, and you may give it in both Arabic and English) and a hex colour (#RRGGBB).

  3. Rename or recolour; the change applies everywhere the label appears.

  4. Delete to retire it. It is stripped from every report that carried it. The reports themselves are untouched.

A space on Professional and above can also define custom fields (text, number, switch or select), which appear on the report page as their own card. They are your own vocabulary for things the fixed fields do not cover: a release number, an environment, a customer tier. Manage them from Manage fields in the inbox header.

Made from the report page, assignment, priority and label changes are all attributable: each writes an audit row naming the report, the person and the time, consistent with the trail status changes already leave. Nothing here happens anonymously.

A bulk action is recorded differently. It writes one row for the batch — which action, how many applied, how many were skipped, and who ran it — not one row per report — and the row does not name the label, the status or the assignee it wrote. So after a bulk relabel you can see that someone applied a label to forty reports at 14:02, but not which label and not which forty, so nothing there answers who put this label on this report. Where the answer has to survive, change it from the report page.

These rows are ordinary activity, not compliance records: they are kept for 30 days by default, rather than the year that role, billing and access changes are held for.