Update sets show committed after cloning dev

[Alex Mikesell]

Hello,

We are on Vancouver and recently cloned over our dev/test instances. As a result I saved my in flight update sets as XML and imported those back into dev post clone to continue work. I'm now trying to move those update sets into the Test environment following the standard procedure(marking update set as complete in dev, retrieiving completed update sets in test) but when viewing Retrieved Update Sets in test they are all marked as committed. Does anyone know why this is? I imagine I can work around this by exporting/importing the latest changes as XML but would like to use standard procedure if available.

[Mark Roethof]

Hi there,

In theory when importing exported update sets, they should be listed in the Retrieved Update Sets and you need to commit it manually. You are mentioning the same update is already committed on test, though in theory that should not got to do with the export/import. Someone must have committed that update set already. Did you check the updated/updated by? Its a recent clone from production I assume, did you also check how it looks like in production, perhaps someone accidently committed it in production and now it was just cloned down?

[Community Alums]

Hi @Alex Mikesell ,

You should have marked the complted set in prod to "Ignore".

As you have no choice now but to do it like that. Since you made a clone, you need to (re)apply the changes in your exported update set. Once you committed a retrieved update set, it will (also) appear in the local update sets, not before.The XML export you make is the Update Set (of course including all customer updates), which is then imported as a "new" updated set after the cloning.  

Steps to preserve Update Sets in DEV prior to cloning DEV from PROD:

1. Export Update Set to XML and Save file locally
2. Clone PROD to DEV
3. Upgrade DEV to new version
4. Import saved Update Sets back to DEV (Load and Commit)
5. Set the Imported Update Set Status back to "In Progress"
6. Create a new Update Set
7. Merge the Imported Update Set with the newly created Update Set
8. Leave the Status of the Merged Update Set to "In Progress"
9. Can the Status of the two Merged Update Sets be changed from "In Progress" to "Complete"

Refer to this link: https://www.servicenow.com/community/itsm-forum/preserve-update-sets-when-cloning/td-p/810249/page/2