Any harm in renaming an update set?

[matthew_magee1]

Hi all,

We have 4 environments:

DEV>TEST>INTEGRATION>PROD

We've recently created update sets in DEV and pushed them to TEST. We realized that with all the update sets, it is hard to distinguish them all into logical groupings.

A lot of the tickets today are simply:

'SC-ticket#-shortdesc-v1

So, in order to help us 'filter' our update sets, we devised a naming convention like:

'SC-v3.2-ticke#-shortdesc-v1

This way we can filter on 'v3.2' and get everything for this particular release.

Is there any harm in renaming an update set that has been pushed from DEV to TEST?

Meaning, we'd update the name in DEV and update the name in TEST so they are identical. The sysIDs would remain the same so I don't see any harm in renaming the update sets in both environments

Any feedback is greatly appreciated-

[venkat2]

There is no harm in renaming the update sets and only SysID values are key in Service now. The update sets are just a package for the updates in xmls and renaming the package name will never cause an issue.

[Pradeep Sharma]

Hi Matthew,

No issues in doing that because the Sys_id will be same which is unique.

Please let me know if you have any questions.