link_issues
Cross-page relationship detection between issues
Overview
Cloning issues often relate to each other across pages. A missing section on one page might be the same section that appeared as 'extra content' on another. This tool creates relationships between issues, helping agents understand patterns and fix root causes instead of symptoms.
How It Works
- Takes two issue IDs and a relationship type.
- Creates a bidirectional link between the issues in the database.
- Supports four relationship types: relocated_content, shared_root_cause, cancels_out, and duplicate.
- Linked issues appear in each other's context, helping agents see the bigger picture.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id |
string |
required | Cloning job ID |
issue_id_a |
string |
required | First issue ID |
issue_id_b |
string |
required | Second issue ID |
relationship_type |
relocated_content | shared_root_cause | cancels_out | duplicate |
required | Type of relationship between the issues |
explanation |
string |
required | Why these issues are related |
What You Get Back
- Relationship ID
- Confirmation of the link created
- Both issues with updated relationship context
Example Use Case
Page A reports 'missing testimonials section' and Page B reports 'extra testimonials section'. These are the same content that was relocated during cloning. Link them as 'relocated_content' so the agent knows fixing one resolves both.
Tips
Use 'shared_root_cause' when multiple pages have the same issue from a shared template or component.
Use 'cancels_out' when one page's 'missing' content matches another page's 'extra' content.
Use 'duplicate' when the same issue appears on multiple pages but should only be fixed once.
Linking issues helps diagnose_fix provide more accurate root cause analysis.