ambacti
Explore workflows

ISSUE TRIAGE · Workflow idea

Help each new bug reach the team best placed to resolve it.

Review new issues that meet agreed triage criteria, compare their descriptions with team responsibilities, and prepare a proposed destination. Keep the current assignment unchanged until an issue owner verifies the recommendation and approves any reassignment.

Make it yours See how it works ↓
A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
New issue ready for triage
Produces
A proposed team assignment with its issue context and rationale, awaiting owner review before the issue is changed.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

A new issue with a description, selected bug label, and triage status

“Assess whether a new bug fits the team’s documented responsibilities, explain the proposed destination, and hold any reassignment for human approval.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps teams reduce manual triage by preparing a considered routing suggestion while keeping issue decisions with their owners.

  1. Identify issues that are ready for triage

    Select new issues with the agreed status, label, and minimum description needed for review.

  2. Compare the issue with team responsibilities

    Use the current team descriptions to prepare a likely destination and note where the issue is ambiguous.

  3. Review the proposed classification

    Have an issue owner check the problem details, rationale, and any uncertainty before deciding where it belongs.

  4. Approve a team reassignment

    Require an authorized person to approve the exact destination before changing an issue’s team.

  5. Review alerts for unresolved cases

    Prepare an internal note when no suitable destination is clear and have a person check its content and recipients before sending.

03 / The result

Something useful.
Something to build on.

A proposed team assignment with its issue context and rationale, awaiting owner review before the issue is changed.

AmbactiWorkflow folio · 5 steps

Review bug triage and team routing

Reviews & approvals · Example outcome

The handoff

A proposed team assignment with its issue context and rationale, awaiting owner review before the issue is changed.

Keep in mind

Issue descriptions can be incomplete, and a team match may be uncertain. Check the issue and team responsibilities; require a human to approve every reassignment, and review any alert about an unclear recommendation before sending it.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Choose the starting team and issue criteria

Define which team’s incoming issues are considered and the label, status, and description requirements.

Document team responsibilities

Maintain clear, current descriptions for each team so reviewers can assess a proposed destination.

Assign triage and change approvers

Name who reviews classifications, approves reassignment, and checks any message about an unresolved case.

Test clear and ambiguous issues

Check well-described bugs, incomplete reports, and issues spanning teams; confirm assignments do not change without approval.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗