Committing update set order

[JohnnySnow]

Hi Team, this is a general query I had in my mind while I was working with updatesets.

Lets consider this scenario. 

There is a catalog item for which the client wants to change the short description and description.

1. I create the update set "Catalogitem Change v1" and capture the SD & description changes.

2. Complete the update set  & move to UAT.

In UAT after testing the client has a change of mind and wants to change the SD & description again.

1. I Create another update set "Catalogitem Change v2" and capture the new changes

2. Complete the update set & move to UAT.

Client is happy.

Now when moving the update set to prod. As per process we would commit the v1 & v2. 

But my question here is, why cant we commit only v2 version directly and skip v1 in prod?

What are issues?

[Sandeep Rajput]

@JohnnySnow Since the changes are limited to short description and description only, you can directly commit v2 on prod. However, from the process stand point, it is always recommend to follow the order and commit v1 and then v2 in sequence.

Hope this helps.