# Intro to Jira Plans | Release management Source: https://www.youtube.com/watch?v=mKQBhP9imzo Recap page: https://rapidrecap.app/video/mKQBhP9imzo Generated: 2025-12-11T19:07:30.779+00:00 --- ## Quick Overview Jira Plans introduces release management capabilities allowing users to coordinate, track, and deploy work across multiple projects and teams toward key milestones, distinguishing between a 'release' as the delivery of a milestone and a 'version' as the group of work items, while also supporting cross-space releases to align dates across different Jira spaces. **Key Points:** - Jira Plans release management helps coordinate, track, and deploy work across multiple projects and teams toward key milestones (0:16). - A 'release' is defined as the delivery of a milestone, while a 'version' represents the collection of work items or tasks associated with that milestone (0:36). - Users can enable the Releases feature within Plan Settings to begin utilizing this functionality (1:03). - Releases can be created directly from the Timeline view by placing an element on the release bar or from the dedicated Releases tab (1:07, 1:46). - The system supports 'Relative to previous release date' for start dates, allowing dynamic scheduling based on a prior release's date (2:08). - Cross-space releases allow grouping multiple releases across different Jira spaces to align their dates, demonstrated by linking 'Donations M1' and 'Volunteers portal M1 - Beta' (2:30, 3:33). - Once changes are made (like assigning work to a release), users must click 'Save changes' to update the plan in Jira (2:49). ![Screenshot at 0:14: The video displays the Jira Plans interface focused on the 'Releases' tab within a 'Pawsitive impact plan', showing existing releases for 'Donations platform' and 'Pawshake mobile app' with their progress status.](https://ss.rapidrecap.app/screens/mKQBhP9imzo/00-00-14.png) **Context:** The video, presented by Atlassian Product Manager Joe Nguyen, serves as an introduction to the Release management feature within Jira Plans. This feature is designed to provide structure for coordinating, tracking, and deploying work across various Jira projects and teams, focusing specifically on aligning progress toward defined milestones, often referred to as releases or versions. ## Detailed Analysis Joe Nguyen introduces Jira Plans' release management, which structures the tracking and delivery of work across projects and teams toward key milestones. He clarifies that a 'release' is the delivery event for a milestone, whereas a 'version' is the group of work items associated with that milestone (0:36). To use this, users must first enable the 'Releases' feature in the Plan Settings (1:03). Releases can be created either by dragging elements onto the release bar in the Timeline view (1:07) or directly from the Releases tab (1:46). When creating a new release, start dates can be set as a Fixed date, As early as possible, or Relative to a previous release date, allowing for dependencies based on prior milestone deliveries (2:08). Furthermore, Jira Plans supports 'Cross-space releases' (2:30), which allows users to group and align the dates of releases spanning multiple Jira spaces, as demonstrated by linking the 'Donations M1' release with the 'Volunteers portal M1 - Beta' release (3:33). Finally, the presentation shows that work items (tasks/epics) can be assigned to specific releases within the timeline view, and any unsaved changes must be explicitly committed by saving the changes in Jira (2:49). ### Release Management Introduction - Jira Plans provides structure to manage workflows for coordinating, tracking, and deploying work across projects and teams toward key milestones - Clarifies 'Release' is the delivery event, 'Version' is the collection of work items - Requires enabling 'Releases' feature in Plan Settings (0:10, 0:36, 1:03) ### Creating Releases - Releases can be created via the Timeline view by interacting with the release marker (1:07) or via the dedicated Releases tab (1:46) - Release start dates offer flexibility: Fixed date, As early as possible, or Relative to previous release date (2:08) ### Linking Work to Releases - Work items (tasks/epics) can be assigned to specific releases directly in the Releases column on the Timeline view (2:20) ### Cross-Space Releases - A powerful feature to group and align multiple releases across different Jira spaces, essential for coordinating dependencies across separate projects (2:30, 3:33) ### Saving Changes - All updates made within the plan environment, such as creating releases or assigning work, require clicking 'Save changes' to persist them in Jira (2:49) ![Screenshot at 0:06: The introductory slide for the presentation, showing the title 'Introduction to Jira Plans' with a focus on 'Release management' and introducing the presenter, Joe Nguyen.](https://ss.rapidrecap.app/screens/mKQBhP9imzo/00-00-06.png) ![Screenshot at 0:14: The Jira Plans interface displaying the 'Releases' tab, showing existing releases grouped by project space, such as 'Donations platform' and 'Pawshake mobile app'.](https://ss.rapidrecap.app/screens/mKQBhP9imzo/00-00-14.png) ![Screenshot at 1:03: The Plan Settings menu showing the 'Features' section where the 'Releases' toggle is enabled, confirming the feature is active for the plan.](https://ss.rapidrecap.app/screens/mKQBhP9imzo/00-01-03.png) ![Screenshot at 1:36: The 'Create release' modal window, detailing required fields like Name, Space, Start date, and Release date.](https://ss.rapidrecap.app/screens/mKQBhP9imzo/00-01-36.png) ![Screenshot at 3:31: The 'Create cross-space release' dialog box, illustrating how to link releases from different Jira spaces, such as 'Donations platform \(GIVE\)' and 'Volunteers portal \(HELP\)'.](https://ss.rapidrecap.app/screens/mKQBhP9imzo/00-03-31.png)