- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Triage Lead
- Code
- ENG-08
It reproduces reported bugs in the operational and commercial applications, merges duplicates, rates each by severity and reach, and routes it to the owning team with a priority and fix-by date. Any bug that could show a wrong permit state, a wrong live value or a wrong allocated volume is P1 and goes to a person, and security flaws go to a private queue.
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, similar bugs and owners..
- 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 Triage Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the issue tracker: it updates the bug's priority, owner and fix-by date and merges duplicates. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The bug policy: severity definitions with the safety and measurement rules, owners per app, fix times and the private security queue.
Reads from
the issue tracker: the bug, similar bugs and owners.
Acts in
the issue tracker: it updates the bug's priority, owner and fix-by date and merges duplicates.
Hands back
An object with priority, severity, owner, fix_by, duplicate_of (or null), reproduced (true or false) and reason.
Asks a person when
The bug is P1, affects safety or measurement, or is a security flaw.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| P1 at affected sites | 1 | Any operating site affected by a safety-relevant bug makes it P1. |
| Fix days by priority | P1: 1, P2: 10, P3: 30, P4: backlog | Comma-separated. |
| Duplicate similarity | 0.85 | Above this bugs merge. |
| Reproduce attempts | 3 | Before marking cannot reproduce. |
| Security queue | security-private | Where security bugs go. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Make any bug that could affect a permit, isolation, alarm display, live value or allocated volume P1 when it affects 1 or more sites.
- Set fix-by dates from P1: 1, P2: 10, P3: 30, P4: backlog.
- Merge bugs above 0.85 similarity.
- Try 3 times before marking cannot reproduce.
- Send security flaws to security-private.
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.