This could be automatically prefixed to friendly name of the deployment.

Sth like "000035"

Could be a simple counter (that I see you have implemented "This is your NNth deployment...").

If the autonumber would pop up automatically then I would not need to figure out a reference and type it myself.

Currently, info that potentially could be used: datetime (too long) , url (way too long)

Currently successful deployment notifications send every success to the specified addresses. Having the ability to specify the source would eliminate the unnecessary notifications to those addresses. We have a use case in which we only wish to send notifications for successful deployments to our production source.

It would be great to see the chosen data hosting option for an account in the 'My Account' area. Without it security audits will not be able to verify what setting was chosen and will have to rely on documentation held elsewhere.

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.

There is no support for Wave Recipes currently and we are not able to deploy dashboards via Gearset and Continuous Integration.

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.

Would it be possible to get a feature where we can download the fields into a csv file?

Currently there is no feature to prevent users in creating their own connections within Gearset.

We need users to follow the permission that was setup on the shared connection. We have only 2 users that have the approval to deploy code from a sandbox to production. As they can set up their own connections then this bypasses our restriction

Having a permission only available to the Enterprise user or a user approved to create connections and delegate access would prevent the bypass of access permissions

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).

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.