Mastering Jira Align’s Dependency Board: From Creation to Resolution in PI Planning

Problem: Cross‑Team Dependencies Hide Behind Jira Links

During Program Increment (PI) planning, teams often discover that the “blocks” or “relates to” links in Jira Software do not surface in a way that lets all ART stakeholders see the full picture. The links sit inside individual issues, and no single view shows who depends on whom, what the risk is, or how the dependency affects capacity forecasts.

Thesis: Treat Dependencies as First‑Class Artifacts in Jira Align

Jira Align solves this by exposing dependencies as dedicated cards on a Dependency Board. Each card is a fully‑featured entity that can be created, updated, and resolved independently of the work items that link to it. This approach gives teams rich metadata, real‑time collaboration, and an audit trail that keeps everyone on the same page.

Creating and Importing Dependencies

Manual Drag‑and‑Drop on the Board

1. Open Program > PI Planning > Dependencies Board. 2. Drag a card from the source team’s swimlane to the target team’s swimlane. 3. In the dialog, choose the dependency type (Blocker, Relates To, Duplicate) and assign an owner.

Import from Jira Software Links

When epics, features, or capabilities are synced, Jira Align automatically creates dependency cards for any blocks or relates to links. To enable this:

• In Jira Align, navigate to Admin > Sync Settings and ensure Blocker and Relates To are mapped to the appropriate Jira link types.
• Verify that the linked issue types are included in the sync scope (Epics, Features, Capabilities).
• Run a manual sync or wait for the nightly job.

Example: A developer creates a blocks link between Epic A (Team Alpha) and Epic B (Team Beta). After the sync, a dependency card appears on the board with type Blocker, source Team Alpha, target Team Beta, and status Unresolved.

Resolution Workflow & Audit Trail

Dependencies move through three states:

State	Description
Unresolved	Needs discussion
In Progress	Teams coordinating
Resolved	Agreement reached; optional notes

Changing a dependency’s status triggers an audit record. The audit log records user, timestamp, and the field changes. Resolution notes are stored only in Jira Align; they do not propagate back to Jira Software comments.

Example API call to update status:

PUT https://your-jira-align-instance.com/align/api/dependencies/12345
Content-Type: application/json
Authorization: Bearer <token>

{
  "status": "Resolved",
  "resolutionNote": "Team Beta will delay feature rollout until Q2"
}

After the call, a GET on /align/api/dependencies/12345 will return the updated status, note, and updatedAt timestamp.

Concurrent edits are detected: if two users modify the same card, the second save prompts a conflict resolution dialog, preventing silent overwrites.

Impact on Capacity Forecasting

Each dependency card shows a Capacity Impact Indicator on the board. Unresolved blockers reduce a team’s forecasted capacity by the estimated effort of the blocked work. This visual cue helps planners identify teams that may need buffer or scope adjustment before committing to the PI.

Example: Team Gamma has 5 unresolved blockers, each estimated at 3 story points. The board calculates a 15‑point capacity hit, flagging the team for potential scope trimming.

Trade‑offs & Limitations

• UI Performance: With >500 active dependencies, the client‑side board can lag. Atlassian recommends filtering by team or status for large ARTs.
• Sync Scope: Only links on synced issue types (Epics, Features, Capabilities) are imported. Story‑level links require explicit configuration and can inflate sync volume.
• Audit Gap: Resolution notes stay in Jira Align. If teams rely on Jira Software for audit trails, this creates a documentation gap.
• Cycle Detection: Bulk CSV imports do not validate circular dependencies; cycles surface only during board runtime, potentially late in planning.
• Custom Types: Adding dependency types beyond the three built‑in categories requires admin configuration and is not portable via standard export/import.

Actionable Checklist for Your ART

1. Enable dependency sync in Admin > Sync Settings and map link types.
2. Train teams to drag‑drop dependencies during PI planning and to use the board’s real‑time collaboration.
3. Set up a routine audit review: Program > Reports > Dependency Audit to verify ownership and status changes.
4. Monitor the Capacity Impact Indicator and adjust PI scope if high‑impact blockers accumulate.
5. Document resolution notes in Jira Align and, if needed, mirror key decisions in Jira Software comments or Confluence.

By treating dependencies as first‑class entities, you gain a transparent, collaborative view that aligns with your PI planning cadence and keeps capacity forecasts realistic.