You can now link releases to organize and manage complex deployment scenarios. Additionally, you can set stage-level release dependencies with built-in checks to prevent duplicate or circular links.
Quick Links
Creating a Sub-release and Associating it with a Parent Release
Release Dependency List View Operations
Parent Release & Sub-release: Break down large release initiatives into smaller, sequential releases using parent–sub-release associations. To set this up, open the parent release, navigate to the Associations tab, and add the required sub-releases.
Select New Release to create a fresh release and link it as a sub-release.
Use Attach to associate an existing release as a sub-release.
Select a release and click Associate.
The release will be added as a sub release.
From the Sub Releases section, you can also perform the following actions:
Detach: Use this to remove any sub release associated with a parent release.
Release Dependency: Use this to view the dependency of the releases.
Delete: Use this to delete a sub release.
Note
Trashing or deleting a Parent Release requires Trash Parent Release permission and scope to all its Sub Releases.
When a Parent Release is trashed/deleted, all associated Sub Releases are also trashed/deleted.
Sub Releases will record: “Release deleted as part of Parent–Child Deletion.”
Dependencies are deleted during trash.
Associations are retained but hidden while the releases remain in trash.
Restore from Trash: A Sub Release cannot be restored if its Parent Release is still in trash.
When restoring a Parent Release, an additional option appears:“Restore the associated sub releases.”Selecting it restores all linked Sub Releases.
The Sub Release association table displays links to trashed Sub Releases to help users restore them.
During trash, associations and scope are preserved, while dependencies are removed.
Alternatively, in a sub-release, open the Associations tab and use the Attach option to link it to a parent release.
Click Attach and select a parent release.
Click Associate.
You can view the dependency between the releases using the Release Dependency option in the parent release.
The stage level release dependency information will also be shown in the workflow instance of a release.
Use release dependencies to define the order in which sub-releases progress across stages. This ensures that one release phase begins only after another has successfully crossed a required stage.
You can configure release dependency from the Associations tab of a parent release.
Drag a connector from a stage in one sub-release and drop it onto a stage in another sub-release to create the dependency. For example, you can drag a connector from the Closure stage of Sub-release 1 and connect it onto the Development stage of Sub-release to ensure the Sub- release 2 will start Development only after Sub-release 1 completes Closure.
To modify the start or end point of an existing connector, hover over a connected stage. The node will highlight in orange. Click and drag the node to a different stage as needed.
To delete a connection, right-click on the connector and click Delete.
Once you are done with the configuration, click Save.
Use the export as PDF option to export the dependency as a PDF.
If you want to undo all the configurations, click Cancel and start again.
Each stage involved in a dependency will display a “Depends On” label within the workflow instance, so you can easily trace where the condition originates from.
From the release list view, you can view the linked releases and their scope.
From the release dependency map in the release details page, you can view how the releases are linked. You can see the parent release, all associated sub-releases, and their dependency as well.
Hover over the info icon on a release to view detailed information about that release.
Hover over a connector to see how dependencies are mapped between stages of sub-releases.
Use the Export as PDF option at the top to download the entire dependency map for offline reference.
Apply release dependency validation for skipped stages: When enabled, the release workflow checks dependencies even for skipped stages. You can enable this option under Release Global Workflow Settings.
Two new options added under Release Users and Roles in Notification.
Release Engineer of Associated Parent Release.
Release Engineer of Associated Sub Releases.
A new closure rule: All sub releases should be closed has been added to the release closure rule to ensure the closure of sub releases while closing a parent release.