Today when you are on a comparison results screen there is an export button that will export the entire list of comparison results to a csv. However the current export does not include a column indicating items that have been selected for the current deployment. Having this column would help in reviewing the list of data outside of gearset.

You offer webhooks for BitBucket and GitHub source control branches (so you can build on-demand if the repository is updated). We use VSTS Git at our organization and this functionality would be really useful for us!

VSTS offers webhook functionality-- see here: https://www.visualstudio.com/en-us/docs/marketplace/integrate/service-hooks/services/webhooks

Please give it a chance!

Please add support for the LeadConvertSettings metadata.
See https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_leadconvertsettings.htm for details

Test jobs are only configured on time basis. When developer commit some changes and it will be deployed, but tests will be done on a time basis in 2 hours for example, so he should wait to know weather tests are passed or not. Or ask the release manager to run tests manually. So, this feature is must have improvement.

It would be great if there was a way to report out by user on the total number of Deployments, Comparisons, Validated packages. I see you have it on the portal, but I am not able to extract the data to analyze it.

Support the ability to group org credentials on the Manage Orgs page by a new Group Name attribute. In managing multiple clients with dozens of PRD and Sandbox orgs it would be extremely helpful to be able to group and filter related credentials by client. However, to expand this feature to support multiple use cases, providing a new Group Name attribute (text) which could contain any value would be fantastic!

Thanks for your consideration,
Mike

Not sure this is a bug or a limitation in the V40.0 SFDC Metadata API but it would appear that Custom Metadata Type (__mdt) listviews are not included in the Comparison (default 66). List Views on other Sobjects are included. Hence they can't be deployed

Build a Jenkins Plugin to integrate with Gearset that would allow triggering CI jobs and/or deployments.

When a dev team work on a shared deployment, it would be nice to work on the same deployment draft, at the same time. At a bare minimum, it would be good to be warned that someone is updating the draft at the same time as you.

It would be great to be able to copy Territory models from one org to another, as per this request in the SFDC Community...
https://success.salesforce.com/ideaView?id=08730000000DgemAAC

Please provide an API for querying deployment info such as friendly names, components, deployment notes, etc...

Currently only the creator (owner) of Schedule Test, Monitor Orgs and Manage Orgs can edit these activities. It would be helpful if we could designate more than 1 Owner for these activities. Similar to granting access to the various orgs (Comparison, Validation& Deployment) it makes sense to also include an Owner access as well.

If this is not possible, having a transfer ownership button would be helpful for each activity.

Thanks!

We sell a managed package and will never include standard objects in a comparison, and absolutely not in source control. When I'm running a compare against source control to check for changes, it will show all of the standard objects as "custom objects" which is not correct. I should have a way to filter out standard objects from the comparison.

Often times I find myself updating 1 or two files since a prior comparison. Rather than refreshing the entire thing which can take a while, it would be nice if I could specify which ones to refresh.

I'm aware that I can set which metadata types to compare, but even in large orgs, the 4 or 5 common ones can still take quite awhile from a full refresh.

Thanks!

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.

Download the zip package at an earlier stage before the analysis has taken place.
In big Orgs with multiple teams working the analysis page takes sometimes to load so it would be a great addition if we can download the zip package file and modify it.

When a CI job fails, the bad code remains in the GitHub repo. I'd like to see a way to revert the commit/PR that caused that failure so that any CI jobs for new, unrelated, commits/PRs won't fail while the developer is working to resolve the issue.

Support automated webhooks into Jira Cloud for:
- Creating a new ticket when automated tests fail
- Updating existing tickets with deployments using the standard Atlassian smart comment format "[TicketID,...] some comment"