Team Triage

Team Triage is a private intake queue for Issues that need review before they enter a Team's normal workflow. A Team settings manager must enable Triage before the queue appears.

When Triage is enabled:

• Triage appears first in the Team sidebar, followed by Issues, Projects, Meeting Minutes, and Views.
• A workspace member outside a visible public Team can submit an Issue to that Team.
• Team members can explicitly create intake from the Team Triage page.
• Each request creates one canonical Issue and one Triage entry.
• The Issue keeps a valid internal status, but stays out of normal Team, My Issues, Project, hierarchy, relation, and saved-view readers while unresolved.
• Only people with access to the Team can see its queue, count, source metadata, or Triage state.

Being able to browse a public Team does not grant Triage access or Issue editing. Processing actions appear only for people with Team Issue work access. Workspace administrators outside the Team may still reach separately authorized Team settings, but that governance access does not expose the queue or its actions.

Submit to a public Team for review

When an enabled public Team accepts outside submissions, an active workspace member outside that Team sees Submit issue for review. The reduced form asks only for Team, title, and description. Status, priority, assignee, Project, estimate, dates, labels, hierarchy, and relations remain under the receiving Team's control.

The submitter may discuss their own unresolved request, but cannot browse the Triage queue, see its count, process other intake, edit operational Issue properties, or manage the Team's archive or views. After resolution, normal Team and Issue access rules apply.

Agent submissions

An agent connected to Integrity, such as Claude Code, can file what it finds into a Team's Triage instead of creating an ordinary Issue. Each submission creates one Issue in Triage from the title and Markdown description the agent wrote. An agent acting for a member of the Team may also set a priority, labels, a Project, and a parent Issue. An agent acting for a workspace member outside a public Team submits only a title and description, like the Submit issue for review form, and its person cannot open the Triage queue.

The agent acts as its person, so permissions and Activity name that person. In the queue row and on the selected Issue, an agent submission shows Agent, the person, and via followed by the name of the agent's connection, for example Agent · Ada Lovelace · via Claude Code. Hover a long connection name to read it in full. Choose Agent in the Source filter to list only agent submissions, and use the source condition Agent in a Triage rule to match them.

Process an agent submission like any other intake: accept it, reject it, snooze it, or mark it as a duplicate. When you accept it, you can add labels such as agent-ready in the Accept dialog. The people responsible for the Team's Triage receive the same Inbox signal as for any other intake.

Agents submit only while the Team's Accept agent submissions setting is on. It is on by default once Triage is enabled; see Team Triage settings. While it is off, an agent's submission is refused and nothing is created. An agent can still create an ordinary Issue in the Team's workflow when you ask it to, whatever the setting says.

Browse and customize the queue

Triage uses one queue view for unresolved intake. By default it shows both Active and Snoozed requests together. Add a Triage state filter for Active or Snoozed when you want a narrower queue. Triage uses the same two-column pattern as Inbox: choose a request from the compact queue on the left and review the full Issue detail on the right. Until you choose a row, the right pane shows the current number of Issues to triage and the create action. The selected Issue key is kept in the URL only after an explicit selection. On a narrow screen, selecting a request opens its detail and Queue returns to the list. The selected request's header names only its key, for example AIL-6, with the Triage icon in orange. Submitted by and the source open the content, level with the top of the Properties card, and Status in Properties reads Triage in the same orange until the request is accepted, rejected or marked as a duplicate; you choose the workflow status when you accept it. A Triage request you add to Favorites shows the same orange Triage icon. Queue rows begin directly below the Triage title header without state tabs, a search row, or another divider. When the current filter has no rows, the left list body stays blank and the right pane provides the empty-state guidance. The queue column is about 400 pixels wide, the same width as Inbox. Each row has three lines. An agent submission starts with the agent mark and any other request with the creator's avatar. The first line is the Issue title, the second is the first line of its description (or No description), and the third names the source: the creator, or Agent, the person and the connection. The key, the priority and the relative creation time are stacked on the right. When the Issue has a due date, its shared due-date badge ends the third line. While a snooze, comment, reply, or wake-eligible property change is saving, its row stays in place on a darker muted loading surface. The Snooze dialog closes as soon as the save succeeds. Snoozed rows replace the creation age with only their remaining snooze duration and clock, use a muted dormant surface and subdued title, and keep that countdown primary-colored; hover and selected states remain visible. Hover the creator to view their workspace identity. A right-click menu provides Accept, Reject, Mark as duplicate, Snooze, and Copy URL. The selected Issue detail exposes the same processing actions in its top bar. Use Filter to narrow the queue by Triage state, status, status type, assignee, creator, priority, estimate, labels, relations, dates, Project, or intake source. Triage reuses the Issue-table filter menu and segmented active-filter header, including searchable filter categories and trailing selection checkmarks. Other Issue-style categories stay visible but disabled when Triage does not yet have a canonical data or behavior contract for them. Filter drafts are private to your browser and persist separately for each workspace and Team. Filter changes mark Display with a dot and reveal its shared Reset and Set default for everyone actions. Active filters appear as chips under the Triage header, for example Source is Agent, with + to add another. Clearing every filter removes that draft. After the last row, a line says how many Issues the filters hide, with Clear Filters next to it; clearing filters restores the queue. Unavailable assignees and creators are removed from saved filters without retaining their profile details.

Use Display to order intake by Added to triage, Priority, or Due date, including ascending/descending direction. The ID and Due date pills control whether those properties appear in queue rows. Changes apply immediately as your private browser draft. When the draft differs from the Team default, use Reset to restore the server filters, ordering, and display properties. Team settings managers can use Set default for everyone to publish the queue's filters together with ordering and display properties to the Team.

Create intake explicitly

Select Create triage issue in the right pane. This opens the same Create Issue dialog used elsewhere, with the Team initially set from the Triage page and Triage selected as the status. You can change to another accessible Team. Triage is a contextual intake choice, not a workflow status: it appears only when the dialog is opened from Team Triage and the currently selected Team has Triage enabled. Changing to a Team without Triage selects that Team's default workflow status, such as Backlog, and removes Triage from the status menu. Ordinary Issue creation never exposes the option, even when the Team has Triage enabled.

Keep Triage selected to submit the Issue to Active. You can set priority, assignee, Project, labels, due date, and estimate before submitting. Submitting new intake refreshes it into the compact left queue without opening its detail; the right pane continues to show the updated count until you choose a row. Selecting a real Team workflow status instead creates an ordinary Issue and does not add it to the Triage queue. Relations can be added after the Issue is accepted. The compact queue header intentionally has no separate Add button.

Review selected intake

Select a queue row to open the normal Issue detail page in the right pane. The Issue breadcrumb, Favorite, overflow menu, properties, description, sub-issues, and Activity use the same surfaces as ordinary Issue detail. While it loads, Triage uses the same Issue-detail skeleton, including your properties-panel preference.

Select Accept to open a create-style dialog filled from the Issue. You can adjust its workflow status, priority, assignee, Project, labels, and due date before accepting. Estimate appears only when the Team enables it. The overflow menu provides Set due date and the reserved Add link item. Add an optional comment, choose Subscribe to updates, and accept; the property draft and transition apply together. The Issue leaves the Triage queue and appears in normal Issue views at the selected workflow status.

Select Reject to add an optional reason and move the Issue from Triage to the Team's Canceled status. The reason appears as a normal Issue Activity comment beside the movement event. Mark as duplicate opens the existing Issue picker. Choosing a target opens the same source-and-target confirmation dialog used by ordinary Issues; confirming moves the source Issue to the Team's Duplicate status without changing the target, shows the normal merged feedback, and records the canonical duplicate relationship in Activity. The duplicate Issue keeps its target banner, while the target Issue lists the duplicate under Duplicates in its Relations card. These actions are permission-gated and close after a successful transition.

Select Snooze to choose an hour, tomorrow, next week, a month, or a custom date and time in the shared calendar dialog. Snooze is Team-wide: the Issue leaves Active for everyone and appears when the queue's Triage state filter includes Snoozed, with its remaining duration. A new human comment, reply, supported property change, or the scheduled deadline returns it to Active once. System, notification, and Triage-generated events do not wake it. Resolving, archiving, or deleting the Issue cancels the pending wake and closes the intake; a restored Issue does not return to Triage on its own, so add it to Triage again if it still needs review. Issue Activity shows a clock for snooze and the Triage icon for wake, and shows the snooze deadline as a readable date and time in your local timezone.

Configure responsibility Team settings manager

In Team Settings > Triage, add current Team members who should monitor new and reawakened intake. Responsible members receive one access-checked Inbox signal, except when they performed the transition themselves, and existing Issue activity email preferences control email delivery. You may designate exactly one responsible member as the static auto-assignee; there is no rotation or workload balancing. Responsibility does not prevent other Team editors from processing the queue. Removing Team membership immediately removes responsibility and clears the auto-assignee selection.

Restricted Teams

Private-Team non-members and direct-share-only Issue viewers cannot discover the Team's Triage route, settings, count, queue rows, or source context. An existing direct Issue share remains governed by the normal display-safe Issue reference contract.