- Industry
- Retail
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Engineering Manager
- Code
- ENG-08
It reproduces, ranks and routes bugs reported from stores, the contact centre, shoppers and monitoring, such as promotions not applying at the till, wrong stock on the site or collection emails not sending. It sets the severity by lost sales and shopper impact and assigns each bug to the owning team.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the issue tracker: the bug reports, related incidents, recent releases and known issues for the systems named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the issue tracker: it updates each bug with its severity, owner and duplicate link. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The bug triage guide: the severity definitions (by revenue at risk, stores affected and shopper harm), the service owners, the known issues, and how to reproduce on the till test lanes and the staging store.
Reads from
the issue tracker: the bug reports, related incidents, recent releases and known issues for the systems named.
Acts in
the issue tracker: it updates each bug with its severity, owner and duplicate link.
Hands back
A list with one entry per bug, each with bug_id, severity (sev1 to sev4), reproduced (true or false), owner_team, duplicate_of (or null), revenue_at_risk_per_hour and reason.
Asks a person when
A bug is severity 1, involves a wrong charge to shoppers, or exposes shopper or card data.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Stores affected that makes it severity 1 | 20 | A till or store system bug in this many stores is severity 1. |
| Revenue at risk per hour for severity 1 (USD) | 25000 | A bug costing this much an hour online or in store is severity 1. |
| Lowest severity for a wrong-price bug | sev2 | A bug that shows or charges the wrong price is at least this severe. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A bug in 20 or more stores, or costing 25000 or more an hour, is severity 1.
- A bug that shows or charges the wrong price, or applies a promotion wrongly, is at least sev2, since it breaches pricing rules.
- Reproduce before ranking; a bug that cannot be reproduced is marked so with what was tried.
- Link duplicates to one bug and route it to the service owner.
- A bug that exposes shopper or card data goes straight to security as severity 1.
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.