Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Track changes for branch merges in Deployment Manager (8.3)

Updated on May 3, 2021

Beginning in Deployment Manager 4.5, you can now associate bugs and user stories with branch merges so that you can track your branch changes. Doing so enables your team to understand the entire life cycle of Agile Workbench items from development to production, ensures that Deployment Manager users can verify that only the correct changes are being migrated, and provides insight into what changes are on each of your candidate systems.

When you start a deployment by submitting a branch into the Merge Branches wizard, you can add a description and associate user stories and bugs from Agile Workbench. This information appears when you view deployment details for the pipeline.

To submit a branch into the Merge Branches wizard and track changes:

  1. In the navigation pane in Dev Studio, click App, and then click Branches.
  2. Right-click the branch and click Merge.
  3. Click Proceed.
  4. In the Application pipelines section, from the Pipeline list, select the application for which the pipeline is configured into which you want to merge branches.
  5. In the Merge Description field, enter information that you want to capture about the merge.
  6. In the Associated User stories/bugs field, press the Down arrow key and select the Agile Workbench user story or bug that you want to associate with this branch merge.
  7. Click Merge.

The following figure shows an example of entering a description and associating a bug with the merge in the wizard.

"Adding a description and associating bugs and user stories in the Merge Branches wizard"
Adding a description and associating bugs and user stories in the Merge Branches wizard

When you view deployment details for the pipeline, the description that you entered and the bugs and user stories that you associated with the merge appear.

"Description and associated changes in deployment details"
Description and associated changes in deployment details

For more information, see Understanding model-driven DevOps with Deployment Manager.

  • Previous topic Upgrade Deployment Manager without running post-upgrade steps (8.3)
  • Next topic Unit test more rule types and configure activity status assertions (8.3)

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us