QA teams: raising a defect and tracking the fix
A tester raises a defect with severity, steps to reproduce and where it was found, attaches a recording or a screenshot, and marks the exact frame or pixel. The test cycle pack runs planned, executing, defects open, retest and signed off. A retest that still fails returns to defects open on a named path, so a fix that did not fix does not disappear into a new ticket.
Raising a defect
The bug work item type asks for severity as blocker, major, minor or cosmetic, steps to reproduce, and the build or environment it was found in. Custom fields add whatever the team also tracks.
A screenshot or a screen recording attaches to the defect. A note on a recording is anchored to a frame. A note on a screenshot can be drawn on it. The developer opens the mark, not a paragraph that tries to describe it.
- Severity: blocker, major, minor, cosmetic
- Steps to reproduce and found in
- Frame-anchored notes on recordings, drawn notes on screenshots
The cycle and the developer side
The test cycle pack runs planned (48 hours), executing (72), defects open (72), retest (48) and signed off. Executing cannot start until the plan and cases checklist is done. Retest has a path back to defects open labelled still failing.
The bugfix pack is the developer side: triage, reproduce, fix, verify and released. Verify can send the item back to fix with the label still broken. The software pack ends QA into a release approval, which is an approval stage the engine enforces.
A defect that turns out to be the same bug as another one is linked to it: a link is typed as relates, duplicates or clones, and blocking stays with the dependency the workflow already reads. The time spent on the fix is logged as typed entries against the item on the day the work was done, and adds up to a personal week and a project total against the estimates.
Honest gaps
A test-run record as its own object is not here; a run is a checklist on the cycle today. We would rather you read that here than discover it after a trial.
Questions that keep coming up
- Can a developer be sent a failing recording with the moment marked?
- Yes. A recording attached to the defect takes frame-anchored notes, and a screenshot takes a drawn note.
- What happens when a retest fails?
- The retest stage has a transition back to defects open labelled still failing. The defect returns without a new ticket.
- Is QA sign-off a real gate?
- On packs that use an approval stage for sign-off, yes: the work cannot leave without a recorded decision. The test cycle pack ends at signed off as a done stage; the software pack uses release approval as the gate.