Triage Items
Triage items are potential work waiting for a decision. They can come from workspace items in review or from bugs and feature requests captured from connected apps.
For the planning workflow, see Triage.
Reviewer
A triage item can have a reviewer. The reviewer is responsible for deciding what should happen next, but the item is not execution work yet.
Reviewers can add comments, ask for more detail, change the reviewer, accept the item, decline it, or mark it as a duplicate of existing work.
Decisions
| Decision | Result |
|---|---|
| Accept | The item moves forward as an initiative or bug. It appears in Backlog unless the reviewer also chooses a different status or assignee. |
| Decline | The item is closed as cancelled. It leaves the default triage queue but remains available through filters. |
| Duplicate | The item is closed as a duplicate and linked to the existing initiative or bug it repeats. |
| Change reviewer | The next reviewer gets the decision. |
Accepted work should have enough title, description, ownership, and status detail for the next planning step. Bugs should have enough description or comments for someone to investigate before they move into execution.
Backlog visibility
Accepting or declining removes the item from the default triage queue. Accepted and declined items can still appear in Backlog when the right filters are enabled. Declined items appear as cancelled.
Duplicate items close against the selected existing work and should not create another roadmap or backlog item.
Fields to check
Review the fields that affect the decision: title, description, source app, reviewer, owner, assignees, status, priority, team, taxonomy, and comments.
Do not treat every field as required. The goal is a clear decision: keep the work, reject it, route it to someone else, or close it as a duplicate.