Question regarding update sets

[Community Alums]

Hi,

I have a small story to tell. Please go through my story and suggest me what would be a good way to follow.

I have a service catalog item XYZ which I created in DEV in sprint 1. The requirements kept on changing until the end of sprint 1 and still more changes are required, and so the story moved to sprint 2.

As it is a critical story, I want to make sure that it works well, I moved the update sets to TEST and I tested in TEST,  right after sprint 1.

In the sprint 2, the catalog item is finally ready in DEV.

At the end of sprint 2 when it is supposed to move to PROD, some member in my team saw the story in TEST and thought, the story is already in TEST and so he moved the update set (this is the sprint 1 updates).

Now in the PROD, the catalog item is with incomplete updates. Now he asked me to create new update set in DEV  with all the updates from DEV and in the next sprint we will move the updates to PROD.

My Question is how to make sure that the new update set will capture every update for this catalog item. What would be the best practice to capture all the updates in a catalog item.

Regards

Suman P.

[Community Alums]

Hi @PrashantLearnIT , @Dr Atul G- LNG ,

The thing I forgot to mention is that, it's only one update set for both sprint 1 and sprint 2. Now it it already made Complete. So, I cannot change it now. I have to create new update set and it has to capture all the updates. What is the best practice to make sure I can capture all the updates.

Regards

Suman P.

[Sandeep Rajput]

@Community Alums If this is just one update set then don't fret, it already has all the changes in it. Simply go ahead and deploy it on Test first and then after testing on the production. 

Also, if the same update set was already committed on test and prod instances then delete the same update set from the retrieved update first and then retrieve it again.

[Dr Atul G- LNG]

Hi @Community Alums / Suman

My experience say merging can be issue, create a new update set, 

- open the old update set , and make 1 small change [ I know it is against policy but that is safe side from thoughts]

- Add another update set ( newly created) and 

Now move these 2 set with parent 

[mihirlimje867]

Hello @Community Alums ,

The best practice is that if you have more than one update set for a story so follow the below steps :

Step 1 :  Create a new update set in Global Application. (use as a parent update set)
Step 2 : Open the update sets in which you have captured the updates. In you case you have two update set (version 1 and version 2)
Step 3 : In these update set, there is "Parent" field add the update set name that is created in the step 1 for both version 1 and version 2 update sets.

Step 4 : One added the parent field for both update sets, now complete the Parent update set. When you complete the parent update set the version 1 and version 2 update set will be automatically completed.
Step 5 : Then click on "Export Update Set Batch to XML", and move this xml to PROD.

Thank you.

[Community Alums]

Hi @Community Alums ,

.

1. Ideally you could just backout the update sets from test and prod, delete the update set from retrieved update sets too.

2. Then move you update sets from dev to test and then from test to prod without any issues. 
you might see some retrieval issues which you can accept.

This way you can ensure your old update set is not present anywhere and updated version is retrieved and committed.

As others suggested you could have captured everything in new update set and move it across to test and prod.

Note- if there was issue in prod you should backout the update set so that you minimize the disruption.

If my response has resolved your query, please consider giving it a thumbs up ‌‌ and marking it as the correct answer‌‌!

Thanks & Regards,

Sanjay Kumar