Copado User Story Bundles (Summer ’21) - Initial Setup Instructions

Updated 2 months ago by Copado Solutions

This document walks you through all the steps to set up the User Story Bundle Summer '21 .

This article assumes that you were not a participant in the User Story Bundles PILOT; if you were a User Story Bundles PILOT participant, please make sure to also review this Article on How to Migrate from User Story Bundles (PILOT) to User Story Bundles (Summer '21).

User Story Object

Page Layouts
  1. User Story Layout
    1. Remove the PILOT field Is_Bundle, if present.
    2. Add the standard field copado.Is_Bundle.
    3. Remove the PILOT field Bundle_User_Story, if present.
    4. Remove the PILOT related list Bundled User Stories, if present.
    5. Add the standard related list Bundled Stories.
      On the Bundled Stories related list, add field Package Version and set Sort By to Bundled Story Name as Descending.
  2. Utility Layout
    1. Assign the Utility Layout to the Utility Record Type
    2. Confirm that the related list Bundle Versions is on the Utility Layout, includes all fields shown below, and is Sorted by Created Date DESC.

Lightning Page

These instructions assume you have created your own custom Lightning Page for the User Story Objects.

  1. Remove the PILOT related list Single Component Bundled User Stories, if present.
  2. Add the standard related list Single Component Bundled Stories.
    1. Set this Component Visibility to Record > Record Type > Record Type Name Not Equal Utility.
  3. Add the standard related list Single Component Bundle Versions.
    1. Set this Component Visibility to Record > Record Type > Record Type Name Equal Utility.

Fields & Picklist values

Ensure the Cancelled picklist value is part of the active values of the Status field on the User Story object. You can tweak the value to be only available for the Utility Record Type, so that normal User Stories don’t have Cancelled as a part of their status values.

Validation Rules

  • There is an out-of-the-box validation in Copado that requires a Cancellation Reason field to be filled if a story is set to Cancelled
    • If you don’t want this behavior, you can deactivate the Validation Rule.
    • If you prefer this behavior, make sure that the Cancellation Reason field is a part of your layout and can be accessed by users who work with bundles.

Field Sets

  1. Fieldset Updates (3)
    1. Update the Bundle Field Set on the User Story Object.
      1. Add these 3 fields from User Story:
        1. Status
        2. Base Branch
        3. Ready to Promote
    2. Update the CBM Fields fieldset.
      1. Add Record Type from the User Story Object.
        1. For now, this will give you visibility on the Pipeline Manager for your Bundles (Record Type = Utility) versus your traditional User Stories (Record Types = User Story, Bug or Incident) that are available for Promotion or Back Promotion
        2. An internal request has been submitted to the Copado Product Team to add copado.Is_Bundle field to this field set for future use
    3. Update the Promotion Related List Field Set.
      1. Add Record Type from the User Story Object.
      2. For now, this will give you visibility on a Promotion’s list of Selected User Stories so that you can distinguish between your Bundles (Record Type = Utility) and your traditional User Stories (Record Types = User Story, Bug or Incident) that are included on the Promotion.
        An Internal Request has been submitted to the Copado Product Team to add copado.Is_Bundle Field to this Field Set for future use.

Search Layout

  1. If you are working in Lightning—add the Create Bundle button to the Default search layout.
  2. If you are working in Classic—add the Create Bundle button to Search Layout for Salesforce Classic > List View

Package Object

Page Layout

Assign the new User Story Bundle Layout to the User Story Bundle Record Type

Lightning Page

  1. Clone the Package_Record_Page (Managed) Lightning Page so that it is editable for future Upgrades; use a Page Label like Package Record Page (Custom)
  2. Save and Activate as Org Default

List Views

  1. Add the Record Type column to your Packages List Views to help discern between your traditional Packages and your User Story Bundle Packages

Package Version Object

Page Layout
  1. Update Artifact Version Layout
    1. Add User Story field beneath Version Name
    2. Move Sandbox Installation URL so it is next to Production Installation URL.
    3. Override the Salesforce Mobile and Lightning Experience Actions.
      1. Add/Remove actions so that the final set of Salesforce Mobile and Lightning Experience Actions only include:
        1. Post
        2. Edit
        3. Lock Bundle
        4. Promote Beta to Released

Lightning Page

As you make these updates, we recommend you save often; activate once only after all upgrade steps are done.

  1. Clone the Package_Version_Record_Page (Managed) Lightning Page so that it is editable; use a Page Label like Package Version Record Page (Custom)
  2. Remove both  Highlights Panel Components and Add a new Highlights Panel Component.
    1. Click Upgrade Now to upgrade the new Highlights Panel Component to Dynamic Forms and choose the option to Start from Scratch.
    2. Add the following Actions to the new Highlights Panel Component:
      1. Edit
      2. Delete
      3. Lock Bundle
        1. Only on this Action , add the following Action Visibility:
          1. Record > Status Not Equal Locked
          2. Record > Package > Record Type > Record Type Name Equal User_Story_Bundle
          3. All Filters are True
    3. Promote Beta to Released.
      1. Only on this Action, add the following Action Visibility:
        1. Record > Package > Record Type > Record Type Name Not Equal User_Story_Bundle
  3. On the top-most Tabs Component, that has Component Visibility Record > Package > Record Type > Record Type Name Equal User_Story_Bundle:
    1. Details Tab of this Component requires no change
    2. Remove the Related Tab from this component.
    3. Stories Selected Tab; the Copado Enhanced Related List on this tab must be customized. (screenshot is quite long, so we have broken this into 3 screenshots)
      Screenshot 1:

      Field Label

      Field Value

      Child related list

      Bundled Story

      Fieldset for the column fields

      Bundle

      Relationship field

      (Leave this blank)

      Specifications about how to order the records displayed

      Id ASC NULLS LAST, CreatedDate

      Number of records to show

      50

      Height

      Auto

      Show row numbers in the first column

      True/checked

      Hide checkbox column for row selection

      True/checked

      Screenshot 2:

      Field Label

      Field Value

      Disable column resizing

      False/unchecked

      Enable infinite loading on scrolling to retrieve more records

      True/Checked

      Hide default actions in column headers

      True/Checked

      Should columns be sortable

      True/Checked

      Enable inline editing

      False/Unchecked

      Hide header

      True/Checked

      Header icon

      (Leave this blank)

      Hide new action

      True/Checked

      Display search filtering

      True/Checked

      Title

      Bundled Stories

      Show subtitle

      False/Unchecked

      Subtitle

      (Leave this blank)

      Show subtitle

      False/Unchecked

      Subtitle

      (Leave this blank)

      Hide footer

      True/Checked

      Is the component directly added to the canvas of the page

      True/Checked

      Set Component Visibility

      No component visibility needed, since it is set on the tabs component.

      Screenshot 3:

      Field Label

      Field Value

      Show subtitle

      False/Unchecked

      Subtitle

      (Leave this blank)

      Show subtitle

      False/Unchecked

      Subtitle

      (Leave this blank)

      Hide footer

      True/Checked

      Is the component directly added to the canvas of the page

      True/Checked

      Set Component Visibility

      No component visibility needed, since it is set on the tabs component.

  4. Metadata Tab should not require any customization; just confirm that the readFromAttachment Component on this tab has:
    1. Name of the Attachment to retrieve = Metadata
    2. Full Profiles & Permission Sets Tab should not require any customization; just confirm that the readFromAttachment Component on this tab has:
      Name of the Attachment to retrieve = Full Profiles & Permission Sets
    3. Destructive Changes Tab should not require any customization; just confirm that the readFromAttachment Component on this tab has:
      Name of the attachment to retrieve = Destructive Changes
  5. The bottom-most tabs component, that has Component Visibility Record > Package > Record Type > Record Type Name Not Equal User_Story_Bundle requires no change.
  6. Perform a final Save and then Activate your Custom Lightning Page and Assign as Org Default.


How did we do?