Currently, when we compare App Menu metadata, the "Depends On" tree is empty, even though it definitely has dependencies on connectedApps and customApplications.

Please add dependency analysis for App Menu metadata,

As feature has moved from pilot to beta in Winter '20 release, looking for support in differencing and deploying the new 'PermissionSetGroup' metadata type.

Allow the custom meta data filters to be categorize or put in folders. You could organize your filters by customer, deployment type, etc..

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.

Right now, the Monitoring job notifications (Slack especially) provide very little detail as to what actually changed.

Ideally, I'd be able to see right in the message (or in a threaded reply), the first X number of metadata changes made. If there are more than that, then providing a direct link to the detail page in Gearset would be great.

As of now, it simply just says "there were changes", with no detail or way to easily see the changes in Gearset...which is not terribly useful.

Currently:
We have to define a single fixed source branch in a CI job, when it has a Git-Source.

Desired:
Option to say "use triggering branch". It should use the branch, where current commit-hook-call comes from.

It should allow Pipelines to test also all development branches e.g. with "Validation only" CI-job.

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.

Currently, when doing a data deployment Gearset will let you know of all the referenced objects from the object you selected. What it doesn't do is the opposite of that - let you know all the objects that reference your object with a lookup.

It'd be great if we could add a filter to utilize some data pulled in a fetch/query during data deployment.

ex. field (TeamMember.Project_Lookup__c in {returned Project results in query in previous step of data deployment).

Currently, when there is an error with an XML metadata file (usually introduced by git merges), Gearset will produce an error, either in the Initializing Comparison, or Checking Deployment stages, stating simply that "An unknown error occurred."

If Gearset instead ran the XML from source control through an XML validator using the Partner WSDL XMLSchema, then we could get file-level validation errors if the XML doesn't conform to what Salesforce's Metadata API will accept.

e.g.:
$ xmlstarlet val -e -s ~/Downloads/salesforce-schema.xml force-app/main/default/profiles/Marketing.profile-meta.xml
force-app/main/default/profiles/Marketing.profile-meta.xml:17108.15: Element '{http://soap.sforce.com/2006/04/metadata}field': This element is not expected.
force-app/main/default/profiles/Marketing.profile-meta.xml - invalid

Please add a link to the test results as part of the notifications sent to Microsoft Teams. The integration with Slack already includes the link so it would be very helpful to have a similar integration in Microsoft Teams.

It would be great to see when a team member last logged in on the user account management page. It would also be great to see like a report or extension on the user page where we can see user usage information. Like number of compares, deployments, etc.. may when last compare was done.

have a way to dump a csv of the description of objects. i need to find a way to see what fields are encrypted.

Currently, if you have a saved filter being used in CI jobs, any edits/changes to that filter are not reflected in the CI jobs that use said filter.

It'd be great if we could isolate filters for CI jobs so that we could edit CI job filters that would then affect every CI job they're being used with instead of having to edit every job and re-select the filter whenever a change is needed.

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.

Ability to see count of items per metadata type at the Comparison Result Page

When a CI job is configured to post to slack, and a job fails, it is very useful to see the message posted with information about what failed (error message, number of components that failed).

However, when a CI job succeeds, it only shows the counts of changed/new/deleted objects.

It would be very useful to have the option to list out what was deployed - this would make it easier for devs/qa users who monitor these slack notifications to understand which deployments are relevant to them at a glance.

A cool feature would be the ability for Data backup to have the ability to select object dependencies when you select a particular object for instances where you want to backup a subset of data and not just your entire org

Looks like with the recent Winter 20 patch sandboxes deploys are failing if custom metadata is included in metadata filter. We had to remove the custom metadata from the filter to get CI jobs to run successfully.

The error was 'Salesforce reported an error (INVALID_TYPE: sObject type 'et4ae5MCOAuthClientDetailmdt' is not supported.)' which isn't even a metadata type in our org.