- For the Releases module to show linked defects on the Quality graphs, how must a defect be linked?
-
a) Linked to requirements
-
b) Directly to the Release or Cycle
-
c) Linked to any entity
-
d) To Tests that are linked to Requirements that are linked to Releases or Cycles
For the Releases module Quality graphs to show linked defects, the defect must be linked to a test, and that test must be linked to a requirement, which in turn is linked to a Release or Cycle. This indirect linking path is required for the defects to appear in Release-specific quality graphs. Direct linking to releases or any entity won't populate these graphs correctly.
In HP ALM/Quality Center, the Releases module's Quality/progress graphs only pick up defects that are traceable through the full hierarchy: a defect must be linked to a Test, and that Test must in turn be linked to a Requirement, which is itself linked to the Release or Cycle. This chained traceability (Release/Cycle → Requirement → Test → Defect) is what the reporting engine walks to compute quality metrics. Simply linking a defect to requirements, or directly to a release/cycle, or to 'any entity' bypasses this required chain and won't surface the defect on those graphs.