Jack Michel
My feedback
4 results found
-
19 votes
-
2 votes
An error occurred while saving the comment An error occurred while saving the comment I came to this idea site to create the same idea. Glad to see it already exists.
-
13 votes
An error occurred while saving the comment I love this idea. Thanks for creating it.
-
2 votes
Here is what I had planned to post about this idea,
"I would love the ability to attach manual deployment steps to a feature branch or pipeline promotion in Gearset, even when there are no deployable metadata changes associated with the work.
The use case is this: some Salesforce changes are UI-only configuration updates that have no metadata representation and cannot be committed to source control. Examples include org-wide email address creation and verification, Process Automation Settings changes, and certain deliverability settings. These changes still need to be deployed across environments in a controlled, documented way alongside related metadata changes.
Today there is no way to attach a feature with 100% manual steps to a Gearset pipeline promotion. The result is that manual steps live outside the pipeline entirely, in Jira tickets or Confluence pages, and the team has no single place to see the full picture of what a deployment requires.
What I would love to see is a way to add manual pre-deploy or post-deploy checklist items directly to a feature branch or pipeline promotion in Gearset, without doing a metadata comparison.
These would not be processed or deployed by Gearset, but they would be visible to whoever is promoting the branch, so nothing gets missed.
This would be especially valuable for teams where a deployment requires a mix of automated metadata changes and manual Setup steps that must happen in a specific order."