Add Releases From Templates

DUE DECEMBER 2019: Release Templates can now be Favorites

DUE DECEMBER 2019: Now, the users of Plutora’s API can:

  • Manage Release Templates:
    • GET /ReleaseTemplates
    • GET /ReleaseTemplates/{id}
    • POST /ReleaseTemplates/createRelease

Adding a Release from a template allows a user to create a Release with pre-populated data, and in the case of Enterprise Releases, potentially a pre-populated Release Manifest with child Releases as well.

Release Templates are set up by administrators.

Adding Releases from templates will trigger email notifications in the usual way.

User Permissions

Users must have the relevant user permissions to create a Release from a template.

Release Type User Permission
Enterprise Create Enterprise Release
Project Create Project Release
Independent Create Independent Release

 

Add a Release from a Template

To create a Release from a template (if you have the relevant user permissions, see above):

  1. Add an Enterprise, Project, or Independent Release from a template in one of four ways:
    1. Directly from a template:
      1. Go to Release > Manager.
      2. Click the Templates toggle button.
      3. Open a template by clicking its Release ID or Release Name.
      4. Click Create Release from Template.
    2. From a template selected in the grid:
      1. Go to Release > Manager.
      2. Click the Templates toggle button.
      3. Click to select the checkbox of a template.
      4. Click + Release From Template.
    3. From the blue navigation bar:
      1. Go to + New > Release > Release From Template.
      2. Select a template from Select Template.
    4. From + Release From Template:
      1. Go to Release > Manager.
      2. Click the Templates toggle button.
      3. Click + Release From Template without first selecting the checkbox of a Release Template.
      4. Select a template from Select Template.
  2. Enter the new Release information:
        1. For Project and Independent Releases:
          1. Type a Release ID. (Mandatory field.)
            The Release ID and Release Name can be the same as each other but must be different from any other Release ID or Release Name
          2. Type a Release Name. (Mandatory field.)
          3. Type a Description or use the template data.
          4. Select a Portfolio Association or use the template data.
          5. Select an Owner.
          6. Select a Release Dependency.
          7. Select an Implementation Date. (Mandatory field.)
        2. For Enterprise Releases without a Release Manifest:
          1. Type a Release ID. (Mandatory field.)
            The Release ID and Release Name can be the same as each other but must be different from any other Release ID or Release Name
          2. Type a Release Name. (Mandatory field.)
          3. Type a Description or use the template data.
          4. Select a Portfolio Association or use the template data.
          5. Select an Owner.
          6. Select an Implementation Date. (Mandatory field.)
        3. Leave the Open the release after creation checkbox selected to open the new Release so you can make further updates.
        4. Click Create.
          • All dates in the new Release or Releases will be shifted depending on the new Implementation Dates.
          • This includes Phases, Gates, Activities, and so on.
        5. For Enterprise Releases with a Release Manifest:

          The Enterprise Release will be created first, then after clicking Create, each child Release with a selected checkbox in the Release Manifest will be created in turn.

          1. Create the Enterprise Release:
            1. Type a Release ID. (Mandatory field.)
              The Release ID and Release Name can be the same as each other but must be different from any other Release ID or Release Name
            2. Type a Release Name. (Mandatory field.)
            3. Type a Description or use the template data.
            4. Select a Portfolio Association or use the template data.
            5. Select an Owner.
            6. Select an Implementation Date. (Mandatory field.)
            7. Leave Open the release after creation to open the new Release or Releases so you can make further updates
            8. Click Create to create the parent Release and open the template of the next child Release with a selected checkbox.
            9. Skip creating child Releases by clicking to deselect their checkbox. (Which can be selected again as long as the creation process has not reached the child Release below the unselected checkbox.)
          2. Create each child Release in turn:
            1. Type a Release ID. (Mandatory field.)
              The Release ID and Release Name can be the same as each other but must be different from any other Release ID or Release Name
            2. Type a Release Name. (Mandatory field.)
            3. Type a Description or use the template data.
            4. Select a Portfolio Association or use the template data.
            5. Select an Owner.
            6. Select a Release Dependency.
            7. Select an Implementation Date. (Mandatory field.)
            8. Leave Open the release after creation.
            9. Click Create on the final child Release to open the new Enterprise Release containing the child Releases in its Release Manifest:
              • All dates in the new Release or Releases will be shifted depending on the new Implementation Dates.
              • This includes Phases, Gates, Activities, and so on.

Back to the top arrow

Be the first to find out about new features. Subscribe to the Release Notes email. Subscribe Now

Was this article helpful?

0 found this helpful.