How to Create a User Story Bundle

Updated 1 month ago by Copado Solutions

Identify How to Best Group User Stories in a Bundle

Before reviewing the steps on how to create the bundle, it’s important that you learn the best practices on how to group user stories in a bundle. 

  1. First of all, you need to define by which criteria you want to bundle them:
    1. Common sprint
    2. Common release
    3. Common project
    4. Common functionality
    5. Common dependencies
  2. Second, you need to define in which stage of the pipeline it is more suitable to bundle the story. It is recommended that user stories get bundled in a stable environment with little or no work in progress (e.g. on the UAT org after a sprint or a release has been successfully tested)
All user stories in a bundle can have different projects and credentials but they need to have the same environment.

How to Create a User Story Bundle

Now that you’ve learned the best practices on how to group user stories in a bundle, let’s see the steps you need to follow to create a User Story Bundle:

  1. Go to the User Story (US) list view.
  2. Select all the user stories that you want to bundle and ensure they all are Ready to Promote.
  3. Click the drop-down arrow for more action buttons and select Create Bundle.
  4. Now enter a name without any space, for the new User Story Bundle.
    USB Name
  5. This generates a package in the Package Version record. In the Bundle Stories section, you can view all the user stories you selected.
package in the Package Version record

  1. After you have confirmed all the details click on Lock Bundle.
  2. The Lock Bundle modal is prefilled based on some pre-defined conditions as explained below.
    1. If all the values of Release, Project and Credentials are the same across all User Stories inside a bundle, the same values are populated in the modal. This is true even if some values are missing, but the rest are the same.
    2. If the values are different across the User Stories in the bundle you will be required to enter the value manually. This holds true even if some values are missing but the rest are different.
    3. If you try to enter a different Environment value manually, it will give you an error.
Lock Bundle


  1. Click on Lock Bundle. The bundle story will be generated and the combined selections of your initial stories will be committed into a new feature branch. This will take place on the org where the stories are bundled. Depending on the type of commits and selections, this can take more than a regular commit, especially if you have many full profile commits.
  2. Now you have a new User Story with these features:
    1. The record type is Utility.
    2. Is Bundle is selected. 
    3. There is a feature branch.
    4. There are US selections attached to this type of US where you can view all the US you selected earlier.
    5. If your initial stories had deployment tasks, the combined deployment tasks will be mirrored on the bundle story.


If you navigate to the original user stories, you will notice the following:

  • The Exclude from CBM and Stop Indexing Metadata in the child user stories are selected:
    • The user stories don’t appear in the pipeline, as only the bundle user story is promoted and back promoted.
  • The Status, Org Credential and Environment fields of the original user stories get automatically updated as the parent bundle user story is promoted to higher environments.

How did we do?