For Omni-Channel deployments, QueueRoutingConfig metadata type is now supported by Gearset. However, corresponding PresenceUserConfigUser and UserServicePresence metadata types are not yet available. This means a secondary Metadata API tool (e.g. ANT, Workbench) or other manual steps are needed to complete an Omni-Channel deployment.

Hoping all supported components for API deployment can be included in diffs for releasing all via Gearset.

I need to set up monitoring against an org that is owned by a user who is no longer active or licensed in the system. It would be incredibly helpful to be allowed to transfer ownership of these orgs between users, rather than requiring someone to delete the org and recreate it under the different owner.

This would allow us to configure our rules in Gearset and then apply the same ruleset during our local development. Until we can upload our own xml config file, please add the ability to export the Gearset rules instead.

see related idea: https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/34668196-allow-pmd-to-be-configured-by-uploading-a-xml-file

In Layouts there are multiple layoutItems. it would be helpful if we could to deploy single <layoutItems> from a Layout without affecting other <layoutItems>.

All user to submit pull request from within Gearset instead of having to jump out to GitHub.

Allowing data deployments in CI jobs. So that configurations in third party apps and B2B Commerce can be deployed as part of CI.

A feature where we can upload our own custom package.xml, where system should pick the metadata for extract & compare and deploy based on the package.xml.

When copying data from production to sandboxes we need to be able to anonymise it for data protection, i.e. GDPR. We also do not want to accidentally email anyone from non-production systems.

After deploying from a Sandbox to a Production environment, you will always see a 'change' for Custom Objects and Custom Fields because there is no Encryption Scheme (for example)

Hello, Could we make a suggestion for an enhancement? For CI Unit Test jobs, could we have a Test suite option? Pulling from the folder inside the metadata? In addition to the "include test from namespaces?"

ANT is unable to change the type on an EmailTemplate from HTML to CUSTOM. To solve that we need to add the EmailTemplate first to the destructive package to have it removed and then add it again with the package.xml
Since this file is not deleted but just changed. It doesn't show up in the deleted items tab.

We should add an option to the "Selected Items"/"Changed Items" list to opt-in for adding that to the destructive.

In org monitoring we frequently get notification about changes an the only thing is a change to the order of the XML elements returned.
The XML is virtually the same but the order of elements returned changed from one day to the other.

It makes differentiating "real" changes from those false positives time-consuming.

It would be great if those kind of changes could be ignored or if there was an option to configure the XML comparison behavior for each monitoring job.

Allow assets with "no difference" to be added to a promotion to allow the same package to be used to both promote as well as sync other sandboxes (without having to manually check if asset was changed in each).

I would like to get some information from the problem analyzer after a CI Job completes as it seems like if it detects a problem during the job it skips deploying some of the components, like user permissions.

Webhooks for CI deployment failures simply say "Deployment failed with (179/180 components deployed)" instead of describing the failure in more detail, including the Object and Error Message

Currently Data Deployments only allow filtering on
[FIELD] = [VALUE]

It would be beneficial to be able to include other logic operators such as:
NOT EQUALS
LIKE
IN
GREATER THAN
LESS THAN

etc.

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

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.

On the "Deployment History" tab, the filter dialog filters on the visible friendly name and items like that. What I would like to do is enter a specific metadata name and have the list filter down to deployments where that specific metadata name was a part of the deployment. This would be useful when getting the question, "when was xyz last deployed?"