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.

[PrashantLearnIT]

Hi @Community Alums 

I recommend recapturing all again in new update set using merge update set from all previous update sets. Add new updates if there are any.

[Dr Atul G- LNG]

Hi @Community Alums 

My thoughts as below:

1. As per me it is a process gap, the reason if story is not fully developed should not be move to test.

2. As sprint 1 is over and sprint 2 started m, then next sprint must hv a new story fot the part which was not completed in Sprint 1.

3. Now as 1 update set is already in Test and deployment team move it to prod , that can be big risk.

Now what best we can do

- Create a Parent update set.

- add Update set 1 and 2 in parent. ( in Dev)

-  Test it fully

- Move parent update set in test ( test in fully as new changes are there)

- In release notes / deployment notes mentioned parent update set along child. 

[Sandeep Rajput]

@Community Alums As a first step, if you do not wish to have incomplete updates on the prod you can always backout the incomplete update set from prod using the Backout UI Action. To know more about Backout, please refer to https://docs.servicenow.com/bundle/washingtondc-application-development/page/build/system-update-sets/task/t_BackOutUpdateSet.html

Instead of recapturing everything in another update set, I recommend merging of Update set 1 from sprint 1 and Update set 2 from sprint 2 and create a new update set. This way only the latest changes will transfer to the merged update set.  For more information on the the merge process please refer to https://docs.servicenow.com/bundle/washingtondc-application-development/page/build/system-update-sets/task/t_MergeUpdateSets.html

Hope this helps.

[Sandeep Rajput]

@Community Alums Do you have any further questions on this topic, if not then please accept the response as accepted solution.