Master Change / Parent - Child Change

[Frank Eck3]

Hi,

I did some research, but maybe I didn't know the right terms. I would like to implement a Master Change or Parent Child Change Relation.

So I have one Parent Change (e.g. DC Move), which consists of serveral child changes.

What is the best way to realized that or for what buzz words I've to search.

Thanks,

Frank

[Hemanth M1 · Accepted solution]

Hi Frank, You can make use of one parent change and having multiple change task this is out of the box feature available in Servicenow You can refer below link : https://docs.servicenow.com/bundle/orlando-it-service-management/page/product/change-management/task/create-a-change-task.html If u really need to implement parent and child change then you need to tweak the logic a bit. Please mark correct if this answered your question. /Hemanth

[Jaspal Singh]

Hi Frank,

There exists an OOB Parent field on Change request table that can be used where you tag it as Parent for all child Change requests.

Also, to get a decent representation you can add the Related list Change Request --> Parent to the Change request form.

Unsure of your actual use case but can't these be considered as Change Tasks rather than a child change altogether.

[Frank Eck3]

Thanks @Jaspal Singh sometimes it's to obvious :-). And no, the customer wants this possibility to structure big changes better. 

[Jaspal Singh]

Yes, business case do vary. So, give a Parent field that exists on Change request table & check. That ideally should suffice the business case.