It'd be great to see the "Friendly Name" in the Deployment Summary page.

e.g. https://app.gearset.com/finished?deploymentId=XXXXXXXXX

And to be able to add/edit the Friendly Name on that page, same as it can be done in the Deployment Summary.

Our use case: We audit all our deployments to make sure they have a name. It would be very helpful to be able to send a Deployment Summary link to a user to tell him to add a name if it's missing.

due to deployment limitations with salesforce destructive changes destructive changes dont necessarily reflect branch to org so these deltas are being marked as differences even though there is no way to fix other than manually in the org. these should be marked as a separate difference type for easier filtering.

I have a small laptop monitor, so screen space is pretty valuable to me when working from home. It can be difficult to do code reviews from a laptop monitor because of the middle bar, which takes up a significant amount of real estate.

I rarely use any of the controls or information in that box. It would be great to be able to collapse or hide it to allow more space for the top panel (list of metadata components) and the bottom panel (selected metadata contents)

Inline Editing of metadata
In order to make our deployment successful we had to download the package, modify the version numbers on the flow definitions, and then compare the local package to the target org. It would be very helpful if we can edit the metadata XML in the UI so we can fix the version numbers.

If a CI job creates a scratch org ; and you configure an outgoing webhook in the CI configuration, the subscribers to that webhook have no way of being able to connect/authenticate to that scratch org.

The typical use case would be to run automated UX testing (Provar, Selenium)

At present, even the CI job creator can't log into the CI-created scratch org let alone any CI webhook

In addition to supporting this, there should be doc on how a downstream webhook can access the scratch org to then do useful work.

Hi Team,

Please add checkbox for validated package as same as deployed ones. that way I can combine package even for validated one's and deploy.

When we validate a deployment then schedule it for deployment. Once deployed we receive a report however the tests run do not show here and you have to back to the validated section to find them - please include the tests run on the final deployment report

It would be super convenient to log into the scratch org directly from the Deployment success page

• From Compare & Deploy sequence


• From CI success

Add Filter/Search to the Salesforce Orgs page. On Deployment History you have a filter that is very handy when sorting through the list to find a specific deployment. I am currently trying to add multiple new dev Orgs for a client and it is hard to sort through them all. Can you add the Filter/Search option on the Orgs page?

After a deployment to a git branch, gearset allows to create the pull request from Gearset. It would be nice to:
1. Have an option to add the pull request URL to the deployment notes
2. Have the capability of add reviewers (users from the git repo) into the Pull Request

Ability to specify test suites when deploying/validating apex classes. It would be easier when there are a large # of test classes involved with a deployment

an additional layer of security and convenience would be to enable Gearset login (that is, login to Gearset) to be done from an enterprise's SSO solution. We use Duo but Okta and others should be supported.

Just like we can login to Salesforce from our enterprise's SSO , we should be able to login to related apps in our suite of enterprise tools via SSO

API to provision users, assign users to connected organisations

It would be hugely benificial to us (60+ connected organisations, 25 employees working in teams for multiple clients at a time) if we could programatically provision/deprovision users and provide access to connected organisations via an api.

At the moment this is error prone manual work that has to be done by someone with high level access (and as such is usually already short on time).

It would be very useful to have a Global Search feature within Gearset. This would be used to search the contents of all metadata objects.

My use case is that sometimes a string has been hardcoded inside a function. The only way to find the function that contains the string is to manually trace through the code. The global search would indicate the function that contains this string.

Another benefit would be to track dependencies for metadata objects that don't support dependency tracking. For example Aura Components, we could search for the component name.

In cases where you have multiple environments, provide an option to define a migration/deployment path; ability to define what environment is the source and what is the target. This will be useful in cases where we have requirement to deploy changes to say production from a specific environment (UAT).

For org monitoring, we can get a notification on either every run, or when the org changes.

Could we also have the option to get notification when the number of static analysis problems increases?

When retrieving metadata from 1GP packaging orgs, the <deprecated> tag appears in the source and, if you deploy to VCS, is preserved. But if you subsequently deploy to a scratch org, and back to VCS, the deprecated tag no longer appears in the scratch org and thus shows up as a diff in the Difference Viewer - confusing the user.

Doc says this tag is reserved for future use and until such time as it is used, suppress

Currently the Jira Ticket Deployment Preferences don't give you enough options to manage the expected behavior with our process. Right now there is too much noise on our tickets and we want the option to reduce that. For example, we do not need to comment on the ticket when attempting to validate deployment, just as we don't need it for failed deployments (which you already have as a feature). We simply want a comment with the deployment notes when a deployment is made since this would reflect the actual system changes that took place with this feature/issue.