Note: Depending on your workspace type, this article may refer to Aha! record types differently than your team does.
Master releases function as parent releases for several child releases. Master releases exist at the parent line level of a workspace hierarchy; releases exist at the workspace level.
Master releases are used in a few common situations:
- Organizations practicing SAFe that are looking to coordinate a cross-product release train
- Organizations looking to standardize the release process across teams, such as a monthly cadence
- Organizations looking to coordinate a cross-workspace launch for a major event, such as an upcoming trade show
A master release contains phases and milestones representing the combined delivery steps. It also contains sub-releases, which are releases at the workspace level. Master releases do not contain features — the sub-releases at the workspace level contain the feature content.
Click any of the following links to skip ahead:
- When to use a master release
- Add a master release
- Add sub-releases
- Visualize the master release
- Master releases across parent lines
- Shipping a master release
When to use a master release
It's important to understand when to create and when not to create a master release. It can be tempting to divide Aha! workspaces into components based on how your team's development resources work, and then use a master release to represent the actual go-to-market workspace release.
This will lead to undue overhead and should be avoided. For more help determining how to set up your workspace and parent line structure, read How to define your workspace. Once you decide how to set up your workspace, if you do need to manage components, you can do so through the use of custom fields.
Add a master release
- To add a master release, make sure a parent line has been selected in your workspace navigation menu next to the home icon.
- Navigate to Releases.
- Click the Add master release button along the top of the screen.
Note: If you do not see the Add master release button, you are most likely navigated to a workspace, not a parent line. Parent lines will show up as bold text in your navigation, similar to how Lifestyle Products is displayed in the above screenshot.
A workspace-level release associated with a master release is known as a sub-release.
When you create a master release, you can choose to automatically add a new sub-release to child workspaces, add existing releases as sub-releases once the master release is created, or do some combination of both.
If you choose to create new sub-releases, they will inherit their names and release dates from the parent master release. If you attach an existing release, the sub-release will retain the name, but the release date will change to match the master release. You can always rename sub-releases later.
To add existing releases to the master release, simply go to Releases > Details or bring out the master release details and click Attach existing release.
Visualize the master release
Once you create a master release, you can visualize it and its sub-releases on the Releases > Overview page and the Roadmaps > Features page. The Roadmaps > Features page is the recommended view to share a visual roadmap of your master release, sub-releases, and the features you wish to highlight.
You can customize what shows by adding releases to the timeline and clicking the X if you do not want to show a sub-release as part of a master release. Then, filter and/or check and uncheck features to focus on only those features that matter most. See Create a features roadmap for more on the Roadmaps > Features page.
Note: The master release will automatically be displayed when sub-releases are selected.
Master releases across parent lines
A master release is created at a parent line level. It can only contain sub-releases belonging to workspaces that are the parent line's children.
This guarantees that a user with the ability to view a master release can also view all of the sub-releases under that master release.
However, the master release can be associated with any level in the parent line hierarchy. So, if you have (or add) another parent line grouping together with other parent lines, you can have a master release that spans all of your workspaces.
Shipping a master release
A master release can have multiple sub-releases, which each might ship independently. For this reason, shipping a master release does not ship child sub-releases.
To ship a master release, first ship the child sub-releases as their work completes. Then ship the master release itself.