Triage queue
Review incoming requests assigned to your team from the Triage queue.
Triage queue
Triage is where target teams review incoming requests — not issue backlog triage. Each team with the triage capability gets a Triage link under its sidebar entry.
Open triage
| Entry point | Path |
|---|---|
| Team sidebar | Triage under your team → /requests/triage?team={teamId} |
| Workspace | Requests → filter or triage views |
The queue title is Requests awaiting triage. Only requests in Triage or Pending show review actions (Accept / Decline / Mark as duplicate).
Triage requires the workspace triage capability (child of requests). If Triage is missing under a team, ask an admin to enable requests and triage for the workspace.
Review actions
Team managers (and others with accept permission) can:
- Accept — approve for the team; optionally set expected completion date
- Decline — reject with optional reason
- Mark as duplicate — point to the canonical request (requester, team manager, or workspace admin)
While a request is Pending, the requester owes the next response — follow up in comments; Pulse moves status back to Triage when the requester replies.
Comment-driven status
Pulse automatically moves requests between Triage and Pending when the target team and requester comment back and forth. Managers can also switch between Triage and Pending directly when clarifying scope offline.
After triage
Accepted requests should link to delivery work:
- Convert to issues and projects
- Mark Done when linked work ships
Next
- Requests overview
- Teams — triage settings under team configuration
- Request templates
Last updated on