Intro to Jira Plans | Dependency tracking

Quick Overview

Jira Plans enables dependency tracking through visual connections on the Timeline view and detailed relationship mapping in the Dependencies view, allowing users to proactively manage blockers, coordinate across teams, and ensure projects are delivered on schedule by visualizing workflow relationships and applying various filtering options.

Key Points: Jira Plans allows users to track dependencies visually on the Timeline view using arrows and lines connecting related work items. The Dependencies view provides a dedicated, focused view of all relationships, showing which tasks 'blocks' or is 'blocked by' others. Users can create dependencies directly on the Timeline by dragging from one issue bar to another, or by using the 'Add dependency' dialog box. The filtering capabilities in the Timeline view allow users to narrow the view to show only 'Work items with dependencies' or those 'Overlapping dates'. The Dependencies view offers advanced grouping options, allowing visualization to roll up by Hierarchy, Initiative, Feature, Story, Sub-Task, or Team. In the Dependencies view, users can filter the relationship display by 'Space', 'Sprint', 'Work Item' type, or 'Issue link type' (e.g., Blocks, Duplicates, Relates to).

Context: This video, titled "Intro to Jira Plans | Dependency tracking," features Joe Nguyen, a Product Manager at Atlassian, demonstrating how to utilize the dependency tracking features within Jira Plans. The demonstration focuses on using both the Timeline view for visual Gantt-style scheduling and the dedicated Dependencies view for mapping complex relationships between work items, which is crucial for coordinating efforts across multiple teams.

Detailed Analysis

The video introduces dependency tracking in Jira Plans, starting with the Timeline view where dependencies appear as lines connecting issue bars, helping users visualize tasks that must start or finish before others. The presenter demonstrates adding a dependency by dragging from one task bar to another and selecting the dependency type, such as 'blocks,' and then selecting the dependent work item from a searchable list. This visual management helps identify potential blockers early. Furthermore, the Timeline view offers filters to isolate specific views, such as showing only 'Work items with dependencies' or items with 'Overlapping dates.' Transitioning to the Dependencies view, the presenter shows a network diagram view of all relationships, which is useful for a high-level focus on inter-team dependencies, such as those between the 'Volunteer experience team' and the 'Donor experience team.' This view also allows users to 'Roll-up' the visualization hierarchy to higher levels like Initiatives, Features, or Teams, offering different levels of abstraction. Finally, the presenter shows the ability to filter the dependency map by Space, Sprint, Work Item type, or Issue Link Type (like Blocks, Duplicates, or Relates to), concluding that these tools ensure teams stay aligned and deliver projects on time by proactively managing cross-team dependencies.

Raw markdown version of this recap