UAE · ENBook a demo
Procure AIEngineeringDecision-maker

Bug Triage Agent

Reproduces, ranks and routes reported bugs.

Bug Triage AgentApplication Engineering
Industry
Procure AI
Department
Engineering
Team
Application Engineering
Kind
Decision-maker
Approver
Triage Lead
Code
ENG-08

It reproduces bugs reported by client users, suppliers and the service teams, such as an approval routed to the wrong approver, an invoice failing match on rounding or a supplier unable to submit a bid, merges duplicates, rates each by severity and reach, and routes it to the owning team with a priority and fix-by date. It sends suspected security flaws, tenant data leaks and payment errors to a private queue.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the issue tracker: the open and recent issues for the components named, their owners, current priorities and the client tenants affected..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to Triage Lead with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the issue tracker: it creates or updates each issue with its severity, priority, owner, fix-by date and duplicate links, in the private queue when needed. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The bug policy: the severity and priority matrix (a wrong payment, a bypassed approval or a cross-tenant leak is always top severity), component owners, fix-time targets, client contract service levels and the known-issues list.

Reads from

the issue tracker: the open and recent issues for the components named, their owners, current priorities and the client tenants affected.

Acts in

the issue tracker: it creates or updates each issue with its severity, priority, owner, fix-by date and duplicate links, in the private queue when needed.

Hands back

A list with one entry per report, each with title, reproduced (true, false or partial), duplicate_of (an issue id or null), severity (S1 to S4), priority (P1 to P4), component, owner_team, private (true or false), fix_by (YYYY-MM-DD or null), workaround (text or null) and reason.

Asks a person when

A bug is rated P1, looks like a security flaw, a cross-tenant leak or a payment error, breaches a client's contracted service level, or the priority overrides the reporter's.

ApproverTriage Lead

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Users blocked that make a bug P150A bug blocking a core journey for at least this many users is P1.
Document value affected that makes a bug P1 (USD)100000A bug that mis-routes, mis-matches or mis-pays documents worth at least this is P1.
Fix-by targets (days)P1: 2, P2: 10, P3: 30, P4: backlogDays from triage to fix for each priority.
Similarity that makes a duplicate (0 to 1)0.85A report at or above this similarity to an open issue is merged.
Private queue for security and data issuessecurity-privateSuspected vulnerabilities and cross-tenant leaks go here, never to the shared board.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Try to reproduce each report in the synthetic tenant matching the stated configuration and record the result; an unreproduced bug asks the reporter for what is missing.
  • Merge a report into an open issue at 0.85 similarity or more, adding the new reporter and client tenant.
  • A bug that blocks a core journey for 50 or more users, or affects documents worth 100000 or more, is P1.
  • A bypassed approval, a wrong payment amount or a cross-tenant data view is always P1 and goes to security-private with the controls owner told.
  • Set fix-by dates from P1: 2, P2: 10, P3: 30, P4: backlog.
  • Route each bug to the component owner; when unclear, route to the Triage Lead.
  • Never paste a client's document data or supplier bank details into the shared issue; reference the record id.

See the Bug Triage Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Bug Triage Agent · Procure AI | Basinwright Industries