UAE · ENBook a demo
IT CompanyEngineeringDecision-maker

Bug Triage Agent

Reproduces, ranks and routes reported bugs.

Bug Triage AgentApplication Engineering
Industry
IT Company
Department
Engineering
Team
Application Engineering
Kind
Decision-maker
Approver
Delivery Director
Code
ENG-08

It reproduces bugs reported by clients and SaaS users from the steps, logs and environment given, merges duplicates, rates each by severity, tenants affected and the client's SLA, and routes it to the owning team. It decides whether a client-project bug is a warranty defect fixed at no charge or a change request, and links it to the support ticket.

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 ticketing and service management system: the linked ticket, similar open bugs, the client's SLA and the go-live date for the engagement..

  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 Delivery Director with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the project management tool: it creates or updates the bug with priority, owner, fix date and classification. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The bug triage guide: severity definitions, fix targets by priority, warranty terms in each SOW, team ownership by component and the private security queue.

Reads from

the ticketing and service management system: the linked ticket, similar open bugs, the client's SLA and the go-live date for the engagement.

Acts in

the project management tool: it creates or updates the bug with priority, owner, fix date and classification.

Hands back

An object with reproduced (true or false), priority (P1 to P4), owning_team, fix_due (YYYY-MM-DD), classification (warranty, change_request, saas_defect or not_a_bug), duplicate_of (or null) and reason.

Asks a person when

The bug is P1, a suspected vulnerability, or classed as a change request the client will be billed for.

ApproverDelivery Director

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Tenants affected for P15A production bug affecting this many tenants or more is P1.
Fix targets (days)P1: 1, P2: 5, P3: 20, P4: backlogFix targets by priority, unless a client SLA is shorter.
Warranty period after go-live (days)90Defects found within this many days of a client go-live are fixed at no charge.
Reproduction attempts3Attempts before it asks the reporter for more.
Security queuesecurity-privateWhere suspected vulnerabilities go, out of public view.

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

Rules it always follows

  • A production bug affecting 5 or more tenants, or blocking a client's business process, is P1.
  • Set the fix target from P1: 1, P2: 5, P3: 20, P4: backlog or the client's SLA, whichever is shorter.
  • A defect against the SOW's acceptance criteria within 90 days of go-live is warranty work; anything else on a client project is a change request candidate for the Delivery Director.
  • Try to reproduce 3 times before asking for more detail.
  • A suspected vulnerability goes to security-private and never into a client-visible ticket.
  • Merge duplicates and link every bug to its support ticket.

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 · IT Company | Basinwright Industries