Currently, if your deployment fails you have two options:

1. Click "back to results"
2. Click "new comparison"

Going with option 1 means it needs to re-load the comparison and then click next and re-run all the analyzers again which can take a varying amount of time depending on the size of the comparison/deployment.

In situations where the deployment failed, but the fix is to change something in the org manually - it'd be great to have an option to simply "retry deployment" from the failed deployment screen and skip the various screens and re-loading.

Be able to delete a comparison run with wrong filters or just keep the latest comparison

It would be great to be able to export the list of unit tests and their respective code coverage in a csv file for further internal processing.

Users should be able to specific and save test classes in the comparison stage so they can be saved in draft deployments. Seems like a waste of extra steps to unclick tests and select tests over and over as you work through a deploy.

also when deploys are combined, they would get all the test classes, again, saving lots of time.

It seems based on the below doc

https://docs.gearset.com/en/articles/3624846-what-does-gearset-s-repo-dependency-cleaner-do

That the repo cleaner will remove permission references related to the following deleted items:

Apex Classes
Tabs
Apps
Object Permissions
Field Permissions

Missing from that list is Apex Pages. It'd be great to have that included to clean up references to the deleted page without having to re-run a 2nd comparison for source control.

The idea is to validate feature branches in repo. For doing this it's necessary to allow specifying source branch by pattern (like feature/*) in "Add CI validation job" menu. The validation should check whether the code breaks the scratch org creation or not. This is valuable due to fragility of scratch org creation process (sfdx force:source:push).

Rather than splitting jobs into Validate and Deploy and ordering alphabetically, allow custom ordering (drag and drop, or custom grouping) in order to maintain logical job sequences including a mix of deploy and validate jobs.

Hi - feature request:
Checkboxes on the validated packages (and probably others) screen so that I can delete validated packages more quickly. One by one is a big pain, and it probably uses your storage... and it definitely clutters our workspace.
Thanks!

After selecting the source org and viewing the metadata comparison filters, there should be an option to only show those types that contain data (the ones that have a number in parentheses). Or in other words... the ability to hide anything that isn't being used.

This would make it much faster to create new comparisons (or troubleshoot existing ones).

It would be nice if there was a way to default the notification for monitoring jobs to 'send notification only when changed'. Right now, if you set monitoring, you get an email a day from that job, regardless if there was a change or not. You have to manually change it otherwise.

Nice to have that setting front and center, available when you select monitoring, as well as have a default value for each org type; Prod, Sand, and Dev.

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.

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.

The ability to delegate access to a scratch org without extending access to the related production environment would be helpful. We have situations where we need developers to build new ideas in a scratch org but do not want to extend the access to the production environment

Hi Gearset😍
Love your deployment product!

We are using salesforce as a ticketing system - any chance you are planning to make a connection to Salesforce records like you did for Jira or Azure?

I would love the have the option to do some things automatically after a deployment, for example:
Attaching the deployment report to the ticket
Updating Status field
Update Environment Field (based on target org name)
Posting a chatter post about the deployment

Thanks!

The comparison screen is great to help admins and declarative users see the changes they made. However, it still requires them to know which metadata to pull based on changes they made.

Source tracking in Sandboxes is in beta and would alleviate this concern.

https://help.salesforce.com/articleView?id=sfdx_setup_enable_source_tracking_sandboxes.htm&type=5

If Gearset could leverage this functionality (potentially leveraging SourceMember object or storing .jsons to track last modified times as local projects store) it would make the complete process easy to use for all alike (pull metadata, select diff, deploy).