You're unable to see the Advanced button on the Commit Changes page with the Destructive
While working in Dev1 Debbie has committed a new custom field “Amount” and a validation rule
“Mandatory Amount” in the same user story. Later, during the sprint, the business analyst decided
that the validation rule should not be included in this sprint but rather moved to the next sprint.
Nonetheless, the custom field must remain and be delivered in the current sprint. How can Debbie
accomplish this?
You have created two different Account page layouts in Dev1, one for sales reps and and another one
for the support team. You have committed the two page layouts on a user story and you are ready to
deploy them to the next environment. However, the sales manager makes a last-minute decision for
his team to continue using the standard Account page layout for now. What is the easiest way to
prevent the sales reps layout from being deployed while deploying the support team layout?
Debbie and Dave were modifying the same Apex class on their individual sandboxes, Debbie
deployed first without any issue, but when Dave tried to deploy, a Git conflict arose, so they teamed
up and resolved it manually with Copado's online conflict resolution feature. What happens when both
user stories are moved to the next environment?