Add a checkbox to chose wheter we want a sfdx compare or an old one (in order to not let gearset chose for us)

When you create a pull request from gearset, the pull request isn't associated with the Azure DevOps work item.

On "Items to include/exclude for Custom application" view, it would be really nice if we could select more than one item at the same time, using SHIFT shortcut.
When clicking on "Named Item", and if you want to select from the 49th line to 63th line for example, and to avoid to select manually 15 lines with 15 clicks.
We could just select the 49th line, and with SHIFT, click on the 63th line to select them.
Thx

In `Deployment history' it would be great if when you choose a target and it opens in a new window. Deploying 48 packages and it is painful.

provide a means of deploying the profile/recordtype/app permissions for lightning record pages without having to deploy the whole app.

Some deployment metadata filters are obvious like Apex classes+profiles but others aren't so, especially to newbies

• Deploying a picklist change on an object w/ recordtypes
• Deploying an app/tab and visibilities therein
• etc.

It would be cool if the custom filtering could link to some recipes to help the user pick all the relevant metadata before tha analyzer runs

Can you please support VS Code extension (ForceCode) source format so that we can use the extension to commit and include in CI jobs.

When deploying email2Case i am unable to choose particular email2Case that i need to deploy and end up choose all the email to case settings. Needed feature to deploy this selectively.

There are times when I'm in an email thread with other developers and I want to share a list of metadata that I'm trying to deploy via Gearset. It would be nice to have a button after a validation or deployment (failure or success) that copies in plain text a list of everything in the deployment. The list not only has the name of each metadata, but also the type of metadata it is.

If the deployment package (especially if target is PROD) contains ONLY Apex classes annotated as @IsTest, then coerce (w/ user confirmation) the deployment to just run those test classes.

This helps avoid errantly clicking the default Deploy and waiting 20-30 minutes for all tests to run. If only test classes are being deployed, by definition, the underlying code hasn't changed and all tests DON'T need to be rerun.

Filters are shared by default. However, if someone changes the filter, I cannot tell what has been changed, who made the change or when it was changed. Ideally, I'd like a version history for each filter.

Ability to do a meta data search like you can in eclipse or visual studio in gearset.

For example search a custom field and where it is used within your org.

Over the past 2 days we ran multiple comparisons between salesforce orgs. Nothing was changed in the target org but some fixes were applied to the source org in order to make the deployment successful. A lot of time would be saved if we had the option to compare the source org to a cached copy of the target org. In this case, the source org was finishing very fast, especially when we used the local file comparison.

We'd like the ability to run static code analysis on all commits to a repo, regardless of the branch name. This would allow us to catch code quality issues early and up front, regardless of the branching model we use.

Example: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow (development is done in feature-* branches, so there's no one branch we can configure a CI job on)

Quite often an Environment needs to be refreshed, but every time it happens all the integration breaks as OrgId changes. Gearset can move metadata and data, which when made together can be a solution for sandbox refresh. Full copy sandbox sometimes takes days, GS will be able to it quite quickly.

When working inside of Gearset, it often alerts you to changes that have been recently made. It would be nice to have these as a separate, consumable, feed. We have a slack channel that we would like to pipe those changes to, for instance.

If you want to deploy the differences of an org on a weekly basis, it would be a great option to take the monitoring results of the last 7 days into a single deployment.
Especially in huge orgs, where comparism takes 30 minutes time to show up, this would ease deployment pretty much.

This would be handy:

If you have a CI job (deploy type) with various configuration (metadata filter, notification, etc) and you want to Duplicate that job, you can't duplicate it to a Validation-Only job. You have to re-enter everything.