bugzilla-triagelisted
Install: claude install-skill topunix/bugzilla-skills
# Bugzilla Triage
Guidance for triaging bugs against the default Bugzilla 5.0+/Harmony data
model: status workflow, resolutions, dependency trees, and duplicates. Every
rule below is sourced from Bugzilla's public documentation or the public
`bugzilla/harmony` source tree — see the `reference/` files for full quotes
and links. If a convention isn't cited to one of those sources, treat it as
outside this skill's scope rather than assumed.
## Status and resolution
Bugzilla's default install workflow only permits specific status
transitions, enforced in code (`Bugzilla::Bug::_check_bug_status` throws
`illegal_bug_status_transition` for anything not in the graph) and defined
by `Bugzilla::Install::STATUS_WORKFLOW`:
```
(none) -> UNCONFIRMED | CONFIRMED | IN_PROGRESS
UNCONFIRMED -> CONFIRMED | IN_PROGRESS | RESOLVED
CONFIRMED -> IN_PROGRESS | RESOLVED
IN_PROGRESS -> CONFIRMED | RESOLVED
RESOLVED -> UNCONFIRMED | CONFIRMED | VERIFIED
VERIFIED -> UNCONFIRMED | CONFIRMED
```
When triaging:
- Don't propose a transition outside this graph (e.g. `IN_PROGRESS` straight
to `VERIFIED`) — it isn't legal in the default workflow.
- `RESOLVED` requires a resolution; moving off `RESOLVED`/`VERIFIED`
back to an open status clears it (`_check_bug_status` in `Bugzilla::Bug`).
- A closed bug reopened to `UNCONFIRMED` also resets `everconfirmed`.
- `IN_PROGRESS` can require a target milestone if the installation has
`musthavemilestoneonaccept` enabled — check before flagging a tri