Issue Strategies

Armada supports different strategies for creating child issues based on your parent issue type and organizational needs.

Available Strategies

Linked Issue Strategy

Creates standalone issues with an “implements” link to the parent.

Parent (Epic)
    ↓ implements
Child (Task in Team Alpha)

Best for:

• Cross-project initiatives
• When teams work independently
• Stories or Tasks as parents

Child Issue Strategy

Creates child issues under the parent in Jira’s hierarchy.

Parent (Epic)
    └── Child (Story in Team Alpha)

Best for:

• Same-project campaigns
• When using Jira’s native hierarchy
• Epics with Stories

Strategy Selection

Armada automatically chooses the strategy based on:

Parent Type	Hierarchy Level	Strategy
Epic	1	Linked Issues
Story	0	Linked Issues
Any	Cross-project	Linked Issues
Epic	Same project	Child Issues

Link Types

When using Linked Issue strategy, Armada uses the “implements” link type:

• Inward: “is implemented by”
• Outward: “implements”

This maintains clear traceability between parent and children.