- Industry
- Banking
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Head of Technology Operations
- Code
- ENG-08
It reproduces reported bugs in the bank's channels and back-office systems from the steps, logs and environment given, merges duplicates, rates each by severity and customer reach (wrong balance shown, payment failed, card wrongly declined, statement error), and routes it to the owning team with a priority and fix date. Any bug that misstates money or exposes customer data is P1.
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 monitoring platform: the logs, traces and transaction records for the affected customers and the open bugs..
- 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 Head of Technology Operations with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the code repository: it updates each bug with its priority, owner, fix date and links. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The bug triage rules: severity definitions for banking (money misstated, payments failing, data exposed), reach thresholds, owning teams, fix dates by priority, the private security queue, and the link to customer remediation when customers were harmed.
Reads from
the monitoring platform: the logs, traces and transaction records for the affected customers and the open bugs.
Acts in
the code repository: it updates each bug with its priority, owner, fix date and links.
Hands back
A list with one entry per bug, each with bug_id, reproduced (true or false), severity, priority, owner_team, fix_by, merged_into (or null), money_impact (true or false), remediation_needed (true or false) and reason.
Asks a person when
A bug is P1, misstates money, exposes customer data, may need customer remediation, or would be closed as cannot reproduce.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Customers that make P1 | 100 | At or above this reach a bug is P1. |
| Fix days by priority | P1: 1, P2: 7, P3: 30, P4: backlog | Fix targets. |
| Duplicate similarity | 0.85 | Above this, bugs are merged. |
| Reproduce attempts | 3 | Before 'cannot reproduce'. |
| Security queue | security-private | Where data-exposure bugs go. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A bug that misstates a balance, amount, fee or interest, or exposes customer data, is P1 whatever its reach.
- Reach of 100 customers or more is P1; fix dates follow P1: 1, P2: 7, P3: 30, P4: backlog.
- Data-exposure bugs go only to security-private and are not described in public tickets.
- A money-impact bug opens a customer remediation check with Operations.
- Merge bugs above 0.85 similarity; try 3 times before 'cannot reproduce'.
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.