Moving Changes Using Update Sets

[rahulyamgar]

Hello team,

I have a quick question on Update Set. Here is the scenario:

1. We made so many changes to a ACL/BR record in ServiceNow captured in multiple update sets. Now we lost the track of Update Sets and we have a final version in Dev ready to be pushed to Production Environment. How do i migrate the changes using the Update Set. 

Any comments would be of great help.

Thanks,
R

[Anurag Tripathi]

You can capture the fresh version in a new update set by making an update to the record, update the description and save. 

It will capture the fresh version on new update set.

Alternatively, you can merge the update sets and it will capture the most recent version automatically.

[rahulyamgar]

Thanks for your response Anurag. But we have little bit different environment. Lets say that we push the update sets to Test environment from Dev environment, and for Production, update sets are pulled from Test environment. Production is going to have all the update sets from Test, but since we have pushed tones of update sets, how do we keep track of which update sets to use/merge and in which order. 

Please provide your thoughts.

Thanks,
Rahul

[AshishKM]

How are you managing overall development,release and deployement work, are you using any external tool like JIRA for stories or keeping all in XLS.

I am sure, you are using normal CHG for PROD release and that CHG must have list of approved use-cases ( or stories ), what's the update set naming standard, how do you know who user has created/or/updated any update set. These are the basic query which you have to discuss with your team and manage the list of update set per CHG some where.

Example : I am using a naming standard for update set, and i can eaisly tell about the update set, module, story, developer and version ( for same story ). e..g   ITSM-INC-SN1209-ABCXYZ-V1 

We are merging the update set at Test instnace level if there are many version of same stories committed from Dev to Test.