We've now released the copying of friendly names and deployment notes over when using the clone package feature for new deployments.

This copying of notes and names works on both the single clone and with the recently released combining multiple deployment packages feature.

Let us know if you've any feedback about its current format.

Regards,

Stephen

please merge: possible duplicate of
https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/33584131-friendly-name-and-details-should-also-clone-and-pr
and
https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/17292943-copy-notes-when-cloning-a-deployment

In my eyes, this is a bug. When we clone a deployment, we have to copy and paste the friendly name and details into the new one. Most times we're performing a clone, it's when we're just moving to a new environment. We typically go from sandbox to staging and then sandbox to production after the changes have gone through QA and UAT. We deploy from the original location to mitigate problems.

You could ultimately change your deployment processes to where a deployment is a record that can be open or closed. If it's open, you can change the source and target and everything remains the same, you just need to compare again and a new audit record of that deployment is created, providing a snapshot of metadata that was used within the deployment. You can then lock down all features when a deployment is set to closed.

Absolutely - especially if you are deploying from dev to qa to prod (2 hops) or dev to integration to qa to prod (3 hops)

This ensures consistency across organizations if a deployment has multiple destinations