qa-defect-management
Defect management discipline (taxonomy, lifecycle, workflows): 3 reference skills (bug-lifecycle-reference, severity-vs-priority-reference, defect-taxonomy-istqb) + 4 platform-workflow skills (jira-bug-workflow-runner, linear-bug-workflow-runner, github-issues-bug-workflow, azuredevops-bug-workflow) + 1 build skill (bug-report-from-failure) + 4 agents (duplicate-defect-finder, bug-report-critic, ci-defect-filer, defect-fix-verifier). Distinct from qa-bug-repro which covers reproduction + clustering + trend narration; this covers triage workflow + taxonomy + severity classification, and closes the lifecycle with post-fix confirmation testing.
Install this plugin
/plugin install qa-defect-management@testland-qaPart of role bundles: qa-starter, qa-role-manual-tester, qa-role-leadership
qa-defect-management
Defect management discipline (classification, lifecycle, tracker workflow): 3 skills (bug-tracker-workflow covering Jira / Linear / GitHub Issues / Azure DevOps, severity-vs-priority-reference with lifecycle + taxonomy references, confirmation-testing-workflow) and 2 agents (ci-defect-filer, defect-fix-verifier). Distinct from qa-bug-repro which covers reproduction, report authoring, and the weekly defect-review pipeline; this covers triage classification, the tracker workflow itself, and closes the lifecycle with post-fix confirmation testing.
Components
| Type | Name | Description |
|---|---|---|
| Skill | bug-tracker-workflow | File / transition / search bugs in the tracker - Jira REST v3 worked in full; Linear, GitHub Issues, and Azure DevOps deep dives in references. |
| Skill | severity-vs-priority-reference | Two-axis defect classification (5×5 matrix with worked examples), plus lifecycle states/transitions and IEEE 1044 / CTAL-TA / ODC taxonomies in references. |
| Skill | confirmation-testing-workflow | Proves a claimed fix reached the build under test via merge-base ancestry rather than a version label, then re-runs the reproduction. Any ambiguous result resolves to BLOCKED. |
| Agent | ci-defect-filer | One-step CI auto-filer: turns a test failure into a deduped bug filed in Jira / Linear / GitHub Issues - four-strategy duplicate search built in. |
| Agent | defect-fix-verifier | Confirmation testing: re-runs a defect's reproduction after the fix merges, verdicts VERIFIED / NOT FIXED / BLOCKED, and transitions the tracker with evidence. |
Differentiation
This plugin scopes defect classification + tracker workflow. Sibling neighbours:
Install
/plugin marketplace add testland/qa
/plugin install qa-defect-management@testland-qaSkills
bug-tracker-workflow
Repairs defect bookkeeping that reports the wrong numbers - a weekly summary showing zero in the top severity band, a 'new defects this week' figure counting items already fixed, duplicates that were never merged, or one script moving issues across several boards whose workflows disagree. Files, transitions, dedupes, and searches bugs through one tracker-agnostic workflow across Jira, Linear, GitHub Issues, and Azure DevOps: authenticate, dedupe-search before creating, classify severity and priority, transition lifecycle states, and wire idempotent CI-driven filing from test failures. Jira Cloud REST API v3 is worked in full in the body (ADF descriptions, runtime transition lookup, JQL triage and duplicate queries, dry-run bulk transitions). Use when tracker data, defect metrics, or cross-board transitions are wrong or need automating.
confirmation-testing-workflow
Procedure for proving that a claimed defect fix actually reached the build under test and actually works. Covers the merge-base ancestry check that proves the running build contains the fix commit rather than trusting a version label, the priority order for choosing which reproduction to re-run, and the VERIFIED / NOT FIXED / BLOCKED verdict table whose governing rule is that any ambiguous, flaky, or unreproducible result resolves to BLOCKED and is never guessed. Scoped to ISTQB confirmation testing (does this specific fix work?), not regression testing (did the fix break something else?), and not triage or severity assignment. Use when a developer has marked a defect Fixed and someone must decide whether it moves to Verified or back to Reopened.
severity-vs-priority-reference
Pure-reference catalog for defect classification: severity (impact on the system / user) vs priority (urgency of fix) on independent axes - the canonical 5-point severity scale (Critical / High / Medium / Low / Trivial), the 5-point priority scale (Immediate / High / Medium / Low / Deferred), the 5x5 matrix with worked S1/P5 and S5/P1 examples, and IEEE 1044-2009 severity classes; plus the full defect lifecycle (ISTQB-canonical states new / open / assigned / fixed / verified / closed / reopened / deferred / rejected / duplicate, allowed and forbidden transitions, tracker vocabulary maps) and the defect-categorisation taxonomies (IEEE 1044 anomaly classification, ISTQB CTAL-TA root-cause categories, Orthogonal Defect Classification) in references. Use when triaging or classifying a defect, configuring a tracker's severity/priority/state fields, reviewing a bug report's classification, or running root-cause analysis.
Agents
ci-defect-filer
Action-taking orchestrator that converts a CI test failure artifact (JUnit XML, Allure JSON, pytest --tb=short log, Playwright HTML report) into a deduped, filed bug in the team's active tracker (Jira / Linear / GitHub Issues) - failure to deduped filed bug end-to-end in one unattended run. Builds the structured spec from the artifact, runs a four-strategy duplicate search (exact-title substring, test-name in body over a 90-day window, normalised stack-fingerprint match, Allure feature/suite tag overlap) with similarity scoring, then creates a new issue or attaches a recurrence comment to the matched one via the tracker workflow. Use when a CI pipeline step fails and the team wants a bug ticket filed automatically, with deduplication, without a manual triaging step.
defect-fix-verifier
Confirmation-testing agent that re-runs a defect's reproduction after the fix is claimed merged and issues a VERIFIED / NOT FIXED / BLOCKED verdict with evidence (ISTQB confirmation testing, synonym retesting). Locates the merged fix commit, confirms the build under test contains it, re-executes the linked repro test (or emits a manual re-verification script), then transitions the tracker (Jira / Linear / GitHub Issues / Azure DevOps) to Verified or Reopened with an evidence comment. Distinct from qa-bug-repro/bug-repro-builder (creates the failing repro BEFORE the fix; this agent re-runs it AFTER). Use when a developer marks a defect Fixed and the team needs the Fixed -> Verified or Fixed -> Reopened transition backed by re-run evidence.