What is the impact of moving update set one after one and moving all together?

[KM SN]

We have created 3 update sets belongs to same story moved them one after one to higher instance that's working fine now we have been told that move all together to another instance.

now the question is when I am moving all together as group out of three which update set it takes into consideration ?? 

[Mark Roethof · Accepted solution]

Hi there,

Best practice is to batch update sets. Not sure why people here are mentioning merging update sets, that's a horrible practice.

Docs page on batch update sets:
https://docs.servicenow.com/bundle/tokyo-application-development/page/build/system-update-sets/hier-...

[KM SN]

As  I said in description if I am moving v1, v2,v3 update sets together(Which are belongs to same story) which version it will consider if I move them as batch ?? 

when we move them one after one obviously it goes with v3 but as we are doing combinedly how it looks like is the issue for me. Pls enlighten me further about this? 

[Mark Roethof]

The system determines the processing order, and checks for collisions, based on the dates the changes were recorded, and on their sequential ancestry.