If we can exclude certain things in the comparison filters, all other newly created things are automatically provided with the CI job that uses my comparison filters.

For example, at the moment in "custom filters", if I select the type "custom object" and disable "all elements", I can filter and choose which objects we want to compare.

-> We need the option to invert the filter. To be able to select the specific objects that do not want to compare and deploy (like "Not: regex: waste_ | QA_ | staging123_").

Option to default to Object View vs XML for metadata types that have it available

For CI jobs we would like to have an option that validation or deployment fails when code analysis identifies any "Error" in the Static code analysis.

When deploying components like workflow rules, workflow field updates, and validation rules, it would be great if the spacing (i.e. carriage returns) did not get lost after deployment. This is especially frustrating for complex formulas where care has been taken to properly indent the formula for easy maintenance.

For large payloads (thousands of artifacts) it can be tedious to try to resolve a few minor issues when 99% of the package will deploy successfully. Having a feature to push stuff that passes validation would be helpful. Included in this in the deployment summary and deployment reports will be a count and list of items that failed validation and were omitted from the package so they can be investigated

Salesforce CPQ uses Data for things that are traditionally done with meta-data. Due to this pricing logic, production configuration information, approval logic, and pretty much the entirety of the package is controlled with data.

Gearset has limited its data migration tool from being able to deploy data to a production org. This renders it useless when working with Salesforce CPQ and has me recommending competitors over Gearset to clients. Gearset is a better UI & workflow than other competitors, but this is a major flaw that should be removed!

Would be great to see the data-deployment history in Gearset UI. Also, the ability to replay them.

everything else is editable; this checkbox is not

I find myself having to go to the original deployed package to copy the description information or coming up with a new description for the cloned package. Would be nice to have this brought over from the original when cloning a package.

Enterprise Users can only "Run Now" Jobs that they own. If the Source and Destination Org are shared, allow other enterprise users to run the job.

For example; when adding new custom fields, you generally have to add the permissions as an additional line item to the deployment. Having a checkbox or something that will have gearset automatically add the permissions associated with the metadata currently in the deployment list would speed up the process. Users should also be allowed to deselect lines that were automatically added.

Please allow to select "when source branch updated" option in the CI jobs section when the source is a custom git repo

Is possible to snip out parts of a source XML file during a compare and deploy run?

I have a file that's changed in both orgs and I just want to import the new bits from one org into the other, rather than delete what's new in that second org.

It would great if browser notifications could be created/enabled to notify a user when a validation or comparison is complete when the user is off the the browser tab where the validation or compare is happening.

It would be nice if the drop-down filter on the deployment history page allowed multi-select. My use case is filtering all successful deployments to production. Seems like it only supports one or the other now.

It would be great if we could configure a notification when a comparison completes. Sometimes comparisons take a long time!

It would be nice to be able to deploy to multiple environments all at once from one source.

It would be incredibly helpful to trigger Gearset comparisons, validations, deployments, etc. from an external source using an API. Our team uses GitHub for our VCS, which provides the perfect opportunity to:
1. design webhooks to validate changes in order to approve a Pull Request
2. design webhooks to automatically deploy changes to an org once the PR is approved.

Additionally, CI tools such as Jenkins, TravisCI, TeamCity, etc could use such an API to design complex builds that still employ Gearset, but use the external tool for additional actions outside of what Gearset provides for their CI features.