As Gearset is run through a web browser, if the browser happens to freeze while a package is being built, you don't have the opportunity to save it as a Draft Deployment. An auto-save feature would allow someone to pick up where they left off, or when the last auto-save was done, without having to start from scratch.

It would be great to have more control over the diff process - particularly to be able to ignore whitespace changes.

If I've made an actual function change to a class, and also auto-indented it, then it would be a lot easier to see the important change if I could hide the whitespace-only changes.

Having the ability to suppress whitespace-only changes on the list of changed objects would be really useful, too.

We have both admins and developers working within our SFDC environments.

Admins typically deploy across environments, so being able to create a CI job to keep the repo updated with these org-to-org changes would be ideal.

Add a Save As or an alternative way to create multiple packages from the same comparison. I have an existing comparison run and I want to stage the deployments, deploying some today and the rest next week. It would be more efficient to save both packages now as I am going through them, saving one for example as Dep120916.1 with half of my selected object and another one called Dep120916.2 with the remaining objects to be deployed later.

I'd like to be able to name 'Pairs' of orgs so I don't have to re-select them, like 'DEV to UAT' or 'HOTFIX to Production'

The metadata compare and deploy is outstanding and works well. What would save configuration and release engineers even more time would be an object data compare / sync. Sometimes, salesforce releases may only require a data migration. Hopefully, this feature will get a few upvotes from the community as well.

Running tests displays overall org code coverage... it would be cool if you could provide individual class code coverage statistics as well, so we could get a good idea of what classes / triggers need attention

In order to support a development pipeline (e.g. Dev Environment -> Staging Environment -> Production) allow Metadata from the source Org to be modified before deployment to the target Org.

e.g. I have a RemoteSiteSetting in source that points at https://dev.example.com and in my staging environment I need this to point to https://stg.example.com

Extend the diff tool to allow the user to perform a merge, creating a new version of the component that contains some changes from the source version and some changes from the target version. This would be very useful in a team development scenario where multiple devs are working on features in individual dev sandboxes and then pushing completed features into an integration sandbox.

Allow those filters we can save to be shared amongst our team!

Sometimes a user may forget to add in a commit message before deploying, so the history in our source control is "no commit message" which is not editable. Can we add a feature to be able to turn on marking commit messages as a requirement for deploy?

We're currently using this tool primarily for nightly unit test monitoring. However, some nights we don't want the tests to run because we'll be doing after-hours upgrades and other maintenance.

As far as we know, currently the only way to 'disable' the automatic test run is to delete/disconnect the app entirely. However this is not ideal, as we have to re-add/re-auth to turn it back on.

If Gearset had a checkbox next to each org/environment that we could enable/disable the job at will, that would be ideal.

Currently, we can only specify a list of users to email, a Slack channel to update, or a Chatter group to post to when a CI job is successful or fails. If there are multiple notifications to a number of people, it's likely they will filter out these messages, so being able to notify the person who the CI Job is most relevant to would be a good improvement.

It seems that Field Sets are deployed by deploying the object that they are related to.

This doesn't work well for me because I have admins changing objects in production, but I often need to deploy a Field Set to go with my code.

Currently, I'm jumping out of Gearset and deploying a Change Set with just the Field Sets, then coming back to Gearset to deploy my code.

It would be nice if I could select just the Field Sets and deploy them without changing anything else related to the object.

In change sets we can pick individual sharing rules to push (specific ones on an object). However through gearset we can only push the whole object.

On comparison screen, would be nice if we can filter on each column on top of standard string filter

Example use case: Show me Custom object with last modified by me with modified date within this week.

Can be achieved if we can filter on "metadata type", "Changed on", "Changed by" Columns

It would be nice if there was a quick way of init'ing a new sandbox that matches either what was in source control or an existing sandbox.

Currently, I need to run a comparison between the existing source and the new sandbox and then I can try the deploy, but it would be nice if the compare step was not needed and I could simply say 'overwrite what is in the sandbox with what is in the specified source'

From what I can determine you are categorizing the differences as follows:
Code in Source, not in Target – Highlighted in Green
Code in Target not in Source – Highlighted in Red
Difference between code in Source and Target – Highlighted in Yellow

When the difference between Source and Target, on a particular line, is only in the formatting. It would be nice if that was highlighted in a different color than yellow (perhaps grey). It would speed up the review of the code knowing a certain color was only a formatting difference.