Triage
Status, priority, assignees, labels, and custom issue types — the fields you use to turn a pile of feedback into a queue.
Every thread carries a small set of triage fields. They're deliberately few, and two of them you define yourself.
Status
| Status | Means |
|---|---|
open | New, nobody's started |
in_progress | Someone is on it |
resolved | Done |
Resolving a thread turns its pin green in the widget, so a reviewer revisiting the page can see what's been dealt with without opening anything. Resolved threads can be reopened.
Priority
low, medium, high, critical. Priority drives Kanban columns, automation
conditions, and the mapping into your issue tracker — critical becomes Urgent in
Linear, and so on.
Leave it unset and AI triage will suggest one on arrival, if it's available on your plan.
Assignee
Any workspace member. An assigned thread shows up in that person's My work, and they get a notification if their preferences allow it.
Labels
Free-form tags you define per project, each with a colour. Labels are for the
cross-cutting things status and priority can't express: regression,
design-review, blocked-on-copy, client-raised.
Manage them in Project → Labels. A thread can carry any number.
Issue types
Issue types are the shape of the problem, and unlike labels a thread has exactly one. They're also project-specific, so an internal admin tool and a marketing site don't have to share a taxonomy.
Manage them in Project → Labels, alongside labels. Each has a name, a URL-safe key, and a colour.
Projects created before custom issue types shipped fall back to a built-in set — broken, wrong text, visual, performance, bug, suggestion, question — which still works and still drives automations.
Sentiment
An AI reading of the tone of a thread: positive, neutral, or negative. It's suggested rather than set by hand, it's filterable, and it's most useful in aggregate — a rising share of negative threads on one page is a signal worth acting on. See AI.
Doing it quickly
The fastest path is the inbox's right-click menu: status, priority, type, assignee, and labels are all one menu away, from either the list or the Kanban board. In Kanban, dragging a card between columns sets whichever field the columns are grouped by.
For anything you'd otherwise do on every single thread, write an automation instead.
Pushing a thread to your tracker
The same right-click menu has an Integrations submenu that creates a ticket from the thread in Linear, Jira, or GitHub. The ticket carries the thread's title, project, page path and URL, type, priority, status, expected and actual behaviour, and the element selector — so the person picking it up doesn't have to come back to Annot8 to understand it.
This is a deliberate action per thread. If you'd rather have every new thread land somewhere automatically, that's a notification integration or a webhook.