Question

You have deployed a story from dev1 to UAT to delete a layout. This layout was never back promoted to dev2, so you don't want this US to show up in the US Behind count. How can this be achieved without losing information?

Answer 1

To prevent the deletion of a layout from showing up in the 'US Behind count' in dev2 after being deployed to UAT from dev1, either merge and selectively undo the deletion in dev2 or label the changeset for exclusion in version control system comparisons.

Step-by-step explanation:

If you deployed a story from dev1 to UAT (User Acceptance Testing) to delete a layout and you want to ensure that this update does not show up in the 'US Behind count' in dev2, there are a couple of strategies you could employ:

• Merge the changes directly to dev2 to synchronize the environments and then undo the specific layout deletion in dev2. This keeps history intact and does not affect the 'US Behind count'. However, it requires careful handling to ensure that only the layout deletion is reversed and no other changes are affected.
• Label the changeset that involves the layout deletion uniquely in your version control system so that it can be excluded from the 'US Behind count' comparisons. Version control systems like Git provide ways to tag or label changesets to filter them out of certain comparisons or reports.

It's important to keep clear documentation of any selective deployments or exclusions to maintain clarity in your deployment process and avoid confusion in the future.