Introduction
You can create three kinds of releases in Plutora:
- Enterprise Release: An Enterprise Release is used to group multiple project releases together under one Release (for example, a release that affects systems across multiple portfolios that have dependencies). Changes cannot be assigned to Enterprise Releases, only to the child Project Releases.
- Project Release: Project Releases are intended to be child Releases of an Enterprise Release, although they can also stand alone.
- Independent Release: Independent Releases are used to represent independent, normally low impact, releases that have no dependencies.
The steps to add Enterprise, Project, and Independent Release are similar with minor differences. To know how these Releases differ from each other, see Enterprise vs Project vs Independent Release.
See Introduction to Release Manager to filter and find templates in the Release Manager grid. There are two ways to add a release:
To add a Release template, see Add/Edit Release Template.
This article provides an overview of steps to add and edit a release in Release Manager using a template. You can add a Release from the template in two ways:
- From the ‘Template’ grid
- Directly from the template
Pre-requisite
You must have the relevant user permissions to add/edit a Release.
| Release Type | User Permission |
|---|---|
| Enterprise | To add: Create Enterprise Release To edit: Update Enterprise Release |
| Project | To add: Create Project Release To edit: Update Project Release |
| Independent | To add: Create Independent Release To edit: Update Independent Release |
To be able to access the ‘Templates’ toggle button, you must have ‘Manage Release Templates’ permission.
Navigation
Release > Manager
From the ‘Templates’ grid
- Navigate to the ‘Release Manager’ page.
- Click the Template toggle button.
- Search and select the template from which you want to create a Release.
- Click
. - On ‘Create Release From Template’ pop up, under 1. Select Template section, the selected template will be displayed. You can choose a different template from the drop-down, if needed.
- The fields under 2. Enter new release information section auto-populates the data from the template. Update the fields as follows:
| Fields | Description |
|---|---|
| Release ID | Mandatory; Update the auto-populated Release ID from the template. |
| Release Name | Mandatory; Update the Release name. |
| Description | Enter a description or use the template data. |
| Portfolio Association | Select a Portfolio Association from the drop-down or use the template data. |
| Owner | Select an Owner from the drop-down. You can choose any user or user group as an owner. The selected owner will be added automatically under the Stakeholders tab as an ‘Accountable Stakeholder’. If you select another Owner, the previous owner will still be an Accountable Stakeholder. |
| Release Dependency | Select a release dependency, if any. This field is editable only in Project and Independent Release. The Enterprise Releases, that are not in an 'End State', will appear to choose from. When editing this field, the 'Phase/Gates Migration' pop-up appears for you to select how the Phases and Gates and their associated Activities and Criteria need to be handled. See 'Phase/Gates Migration' options for more details. |
| Implementation Date | Mandatory; Select an Implementation Date for the Release. All the phases, gates, activities, and criterion dates will be adjusted based on this date. |
| Open the release after creation | Selected by default. If remain selected, the Release will open after creation so that you can make further updates |
- Click
. This button enables only after you select the Implementation Date for the Release.
A new release will be created and ready for updates.
See What’s Next for the next step after creating a new release.
Directly from the template
- Navigate to the ‘Release Manager’ page.
- Click the Templates toggle button.
- Search and select the template from which you want to create a Release.
- Open the template by clicking its Release ID or Release Name.
- The Release Template pop-up displays. Click
at the footer of the pop-up.
Another pop up ‘Create Release From Template’ displays with the template details selected by default. Fill in the fields in the pop-up to create a new release. For details, refer to the table in the above section.
The new Release is now created and available in the ‘Releases’ grid.
What’s Next
The next step after creating a new release is to add and manage Phases and Gates to the release.
More Information
Enterprise vs Project vs Independent Release
| Enterprise Release | Project/Independent Release | |
|---|---|---|
| Purpose | An Enterprise Release is used to group multiple project releases under one Release (for example, a release that affects systems across multiple portfolios that have dependencies). | Project Releases are intended to be dependent on the Enterprise Release, although they can also stand alone and Independent Releases are used to represent independent, normally low impact, releases that have no dependencies. |
| Icon |  | Project Release:  Independent Release:  |
| Relation | Acts as a ‘Parent’ Release to the Project and Independent Release | Acts as a ‘Child’ Release if linked to the Enterprise Release. Also known as ‘Non-Enterprise Release’. |
| Release Manifest tab | The Release Manifest tab allows you to add Project and Independent Releases to the Enterprise Release. | Release Manifest tab is not available. |
| Changes tab | Changes cannot be assigned to Enterprise Releases. | You assign changes to Project/Independent Release which, in turn, can be linked to the Enterprise Release. |
| Child Push | Child Push feature creates a duplicate of the selected Phase/Gates and associated Activities/Criteria in the Child Release | You cannot push Phases/Gates from Project/Independent Release to Enterprise Release. |
| Ignore Child | ‘Ignore Child’ feature, when checked, ignores the duplicated Phase/Gate in the Child Release. | You cannot control the Enterprise Release Phase/Gate from the Child Release. |
| Phase/Gate name | You can centrally change the Phase/Gate name, that is pushed to the Child Release, from here. | You cannot update the Phase/Gate name that is pushed from Enterprise to Child Release. |
| Environment Bookings | There is no limitation in booking the Environments. | Only those Environments whose system is linked to the respective Child Release is available for booking. |
| Release Framework | Mutilple Release Framework options available for Activities:
| Standard Framework for Activities. |
Create Enterprise Release from Template
If you are creating an Enterprise Release from the Template, under 1. Select Template section in the ‘Create Release From Template’ pop-up the linked Child Release Template(s) will also be displayed. The child Release Template(s) will be selected by default. You can opt to deselect those templates as per your Release requirements.
If you proceed with the child Release Template(s) selected, you need to enter the details for the new child Releases as well.
