1.8Linking Defects to Context

Good defect tickets are connected, not isolated. Every bug exists in a web of context: it was caused by a code change, it blocks a user story, it relates to an epic, and it will be fixed by a pull request.

Bug: SHOP-789 (Checkout 500 on expired coupon)
  |-- Caused by: SHOP-654 (Coupon validation refactor)
  |-- Blocks: SHOP-800 (Coupon testing story)
  |-- Related to: SHOP-567 (Coupon expiry epic)
  +-- Fix PR: github.com/org/repo/pull/123

These links create a web of context that helps everyone understand the full picture. When a developer opens SHOP-789, they immediately see which story introduced the bug, which epic it belongs to, and which PR will fix it. When a product owner looks at the epic, they see all related defects and their statuses.

Link Types in Jira

Link Type	When to Use	Example
is blocked by	Cannot proceed until the linked issue is resolved	Test execution blocked by environment bug
blocks	This issue prevents progress on the linked issue	Bug blocks story completion
is caused by	Root cause relationship	Bug caused by a specific story or commit
relates to	General relationship	Bug relates to an epic or feature area
duplicates	Same issue reported twice	Link and close the duplicate
is cloned by	Issue copied for a different project or version	Cross-project tracking