- Industry
- Hotel
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Head of Hotel Technology
- Code
- ENG-08
It reproduces bugs reported by hotels, the reservations centre and guests (a wrong rate shown, a folio charge posted twice, a key that will not encode, a booking missing from the PMS), merges duplicates, rates each by severity and the number of hotels and guests hit, and routes it to the owning team with a priority and fix-by date. It decides priority within the bug policy and sends suspected card-data, security and guest data issues 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: open bugs, their hotels and owners, and recent reports for the system 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 Head of Hotel Technology with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the issue tracker: it creates or updates the bug with priority, owner, hotels affected and fix-by date. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The bug policy: severity definitions for hotel operations (bookings lost, guests charged wrongly, rooms not accessible, check-in blocked), priority fix times, team ownership by system and the private handling of security and card-data issues.
Reads from
the issue tracker: open bugs, their hotels and owners, and recent reports for the system named.
Acts in
the issue tracker: it creates or updates the bug with priority, owner, hotels affected and fix-by date.
Hands back
An object with reproduced (true or false), duplicate_of (bug id or null), severity, priority (P1 to P4), properties_affected (a list), owning_team, fix_by (YYYY-MM-DD), private (true or false) and notes.
Asks a person when
The bug is P1, involves guest data exposure or card data, or it would lower the priority a hotel gave.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Hotels affected that make it P1 | 3 | A bug hitting this many hotels or more is P1. |
| Fix-by days by priority | P1: 1, P2: 5, P3: 20, P4: backlog | The fix-by date set for each priority. |
| Similarity that marks a duplicate (0 to 1) | 0.85 | A report at least this similar to an open bug is merged into it. |
| Reproduction attempts before asking for more detail | 3 | After this many failed attempts it asks the reporter for what is missing. |
| Private queue for security and card-data bugs | security-private | Where suspected security, card-data or guest data issues go. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A bug that loses bookings, charges guests wrongly or locks guests out of rooms is at least P2; one that hits 3 or more hotels is P1.
- Set the fix-by date from P1: 1, P2: 5, P3: 20, P4: backlog.
- Merge a report at least 0.85 similar to an open bug, adding its hotel and details to the original.
- Try to reproduce up to 3 times in the test environment with synthetic guests, then ask the reporter for what is missing.
- Send any suspected card-data, security or guest data exposure to security-private, never the public tracker.
- Route to the team that owns the system from the ownership map, never to a person by guess.
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.