changing update set state from completed to in progess

[Hitesh targe]

Hi,

would like to understand more about update set.

what will happen if we change the update set from completed to in progress? Any issues?

Thanks

[sachin_namjoshi]

It's not best practice to reopen completed update set.

You should create new update set and capture updates in new update set.

You can merge update sets before moving to next instance.

Even if change update set from completed to work in in progress, your changes will be captured in your same update set.

Regards,

Sachin

[Chander Bhusha1]

Hi

Ya there will be any issue as I have done it for some minor chages which I skipped .

But As sachin told it is not a good practice.

Thanks .

[Jaspal Singh]

Hi,

No issues as such if you have not promoted the update set in some other instance. If you have already committed it in some other instance & then you try to get it change to work in progress & then mark it complete & then push it to other instance & commit it may not have the latest updates that were made when the completed update set was opened again.

Also, it is not a best practice to have update set opened once completed.

[Dave Smith1]

would like to understand more about update set.

What do you know about them so far?   What else would you like to know about them?   Have you read the documentation on them?

what will happen if we change the update set from completed to in progress?

You're allowing it to be selected as an update set when making changes.

 Any issues?

Generally... no. Not from a technical viewpoint.

From an organisational or procedural viewpoint, an update set is marked completed to signify it's a self-contained set of changes.   Re-opening it to add something more isn't good practise and can cause issues, such as:

• when retrieving completed update sets onto another platform, the one you've re-opened gets skipped.
• the developer who closed the update set may become upset at finding someone's interfered with something they marked complete.
• the update set may have already been copied over and used for a deployment already, so you're bundling more changes into a closed package, which may/may not work and ends up forking the rollout paths
• it could violate policy governing a number of completed user stories per update set, as it's interfering with the content.

Best practise recommends leaving completed ones alone and opening another one.   Completed sets can always be merged later (but the tools are clunky).