Best way to rename assignment groups

[Alex Saager1]

Hello,

With my organisation recently having a re-design, one of our teams have now been split into 3 and I wanted to know the best way to move active tasks to the new teams, we have about 90 tasks with the current team including incidents, requests, changes, catalog tasks etc.

Is it as simple as creating the new groups and them re-assigning the current active tasks?

Many thanks 

Alex

[Steven Parker]

These are the steps we use when renaming a group that was imported from AD.  Since assignment groups are reference fields, the task, incidents, changes, etc.. will update automatically once the group name changes.

- Disable Listener and LDAP Scheduled Loads in PROD to prevent group from updating in PROD.

The following steps to be performed on DEV first then PROD
- Modify Group Name in ServiceNow DEV
- Modify Group Name in Active Directory
- In DEV, Sync Active Directory to ServiceNow after modifying the group name in both places
- Confirm any open tasks for that group and workflow task update appropriately to the correct group name in DEV.

- If you used the actual group name in any scripts (and not the group sys_id) then those scripts will need to be updated.

If testing is successful in DEV, complete the following in PROD:
- Re-enable Listener and LDAP Scheduled Loads in PROD to prevent group from updating in PROD.

- Perform LDAP sync for groups so the name will change