Continue working on a completed Update set

[DevtoSME]

can you continue working on a update set by setting it to "in progress" after you already previously marked it as complete?

[Mohith Devatte]

hello @Joyea Mells ,

see ideally we can do it but it's not recommded to do it as its not the best practice.

Reason : if you make it in progress and capture some update and close it and take the xml of the update set and load it in the upper instances it will load the update set with same name in the upper instances  which might lead to confusion  to guess the right update set version amongst the original and the duplicate one and also the time stamps for the customer update will be different.

So best practice is to create a second version of your update set and merge it with the previous update set or batch it and then move it 

please mark my solution correct if it helps you

[Mohith Devatte]

@Joyea Mells did this help you ?

if yes please mark the answer correct and close the thread so that it helps the future readers with same query and pushes to solved queue

[DevtoSME]

Hi thank you for this answer.

in this situation i am in the dev instance and i have not moved the update set to test or prod. will it still be an issue even if its best practice or should  use best practice and use a new update set to add changes and merge them together.

[JV2]

If you're still in Dev and have not promote it to any sub-prod instance, you can just re-open it and continue working on it. No harm is done by that. Even if you have moved it to other instances, if you have not Committed it yet, you could still delete it from this other instance, re-open it in Dev and continue working.

The "best practices" point more to cases when you have already move it other instance and have committed it. After that, you definitely have to create a version 2 of the update set.