Bulk Update Releases

Users can save time by bulk updating release information, stakeholders, and activities.

When bulk updating a field or a tab, data will either be replaced (in the case of text fields and drop-down menus) or added (in the case of Stakeholders and combo boxes). Data cannot be bulk deleted.

Bulk Update Releases

Users must have the Update Release user permission to bulk update Releases. 

To Bulk Update Releases:

  1. Go to Release > Manager.
  2. Click the Releases toggle button (if present).
  3. Click to select the checkboxes of two or more Releases (left column of Release Manager).
  4. Select Bulk Update from the Action drop-down menu.
  5. Perform one or more of the following actions:

    1. Click the Release Information tab and update:
      1. Release Type.
      2. Release Status: If the Enable Release Workflow checkbox has been checked in the Release Status Customization, the Status field will be grayed out until a Release Type is selected.
      3. Portfolio Association: Users can only select the Portfolio Association they have been assigned or sublevels of that Portfolio Association.
      4. Risk Level.
      5. Release Location.
      6. Implementation Date.
      7. Phases: The Start Date and End Date fields will be grayed out until a Phase is selected.
      8. Gates: The Start Date and End Date fields will be grayed out until a Gate is selected.
    2. Click the Additional Information tab:
      1. The Additional Information tab contains custom fields, which administrators have added using Release Custom Fields Customization. These fields will vary between each Plutora installation. Please consult your administrator for the procedure for filling in these fields.
    3. Click the Systems tab:
      1. Live Search for Systems or Portfolio Associations or view a tree menu of Portfolio Associations by clicking the right side of the drop-down menu.
      2. Drag and drop Systems from the Systems Available  panel into:
        1. Code Implementation Dependency: To show that the System is impacted by the Release.
        2. Regression Verification Dependency: (If only Project or Independent Releases are selected.) To show that the Release poses a regression risk to the System.
        3. The up-to-two custom Systems Subtypes.
    4. Click the Stakeholders tab to add Stakeholders:
      1. Click Add Stakeholders.

        When users are added as stakeholders more than once, they will appear as a stakeholder only once with all their Roles and Stakeholder RACI Roles merged.
        For example, if a stakeholder with Role A and all the RACI Roles was added again with Role B and no RACI Roles, the stakeholder would appear only once with Roles A and B and all the RACI Roles.

      2. Select a name from the Name drop-down menu.
        You can also select User Groups.
      3. Select a role from the Role drop-down menu.
        Administrators can add roles using the Stakeholder Role Customization.
      4. The Email field is not editable.
      5. Click to select a Stakeholders RACI checkbox.
        You can add multiple Accountable stakeholders. The first Accountable stakeholder will appear next to the Release in the Release Manager column in Release Manager.
      6. Click Add & Close.
      7. Click Save.
      8. If you need to remove a Stakeholder you have just added via Bulk Update, click to select the Stakeholder and click Remove.
    5. Click the Activities tab and bulk update Activites and Criteria:
      1. Filter using the Activites and Criteria checkboxes.
      2. Click to select the checkboxes of the Activities and Criteria.
      3. Click to select a user or user group from the Assigned To drop-down menu, to add a new user or user group to the selected Activities and Criteria.
        Users can select from all the Stakeholders from all the selected Releases.
      4. Click to select a status from the Status drop-down menu, to assign a new Status to the selected Activities and Criteria.
  6. Click Update.


Back to the top arrow

Be the first to find out about new features. Subscribe to the Release Notes email. Subscribe Now
0 found this helpful.