Please add WebStoreTemplate as a metadata type

https://ej2.syncfusion.com/vue/documentation/drop-down-list/filtering/
Much like the above, when searching through many fields it can be tedious

We want to restore certain fields instead of all data into Salesforce

Please include columns for the components Label and API Name along with the Item Type and Display Name when exporting to CSV.

Use Case - We use the Export results as a formal Deployment Log that we sharing with a Client's project team. In that log, we include the component's Label, API Name, and metadata Type. Most recipients of this Deployment Log are unfamiliar with the API Name which may not even closely match what the Label is. Having both in this Log would greatly enhance this understanding.

Thanks in advance!

In cases where you have multiple environments, provide an option to define a migration/deployment path; ability to define what environment is the source and what is the target. This will be useful in cases where we have requirement to deploy changes to say production from a specific environment (UAT).

If a CI job creates a scratch org ; and you configure an outgoing webhook in the CI configuration, the subscribers to that webhook have no way of being able to connect/authenticate to that scratch org.

The typical use case would be to run automated UX testing (Provar, Selenium)

At present, even the CI job creator can't log into the CI-created scratch org let alone any CI webhook

In addition to supporting this, there should be doc on how a downstream webhook can access the scratch org to then do useful work.

For org monitoring, we can get a notification on either every run, or when the org changes.

Could we also have the option to get notification when the number of static analysis problems increases?

When retrieving metadata from 1GP packaging orgs, the <deprecated> tag appears in the source and, if you deploy to VCS, is preserved. But if you subsequently deploy to a scratch org, and back to VCS, the deprecated tag no longer appears in the scratch org and thus shows up as a diff in the Difference Viewer - confusing the user.

Doc says this tag is reserved for future use and until such time as it is used, suppress

UX suggestion (tie list of scratch orgs to URL)

If you use Gearset to create a scratch org, the list of scratch orgs on the My Connections page does not tie to the visible URL of the scratch org you log into

This gets to be a real issue for the multi-tasker who might have several scratch org tabs open at once but has no way of knowing which one is which vis-a-vis the Gearset enumeration of how the scratch org was logged into the first place. Drilling into the user's name is too clunky

We would like to only see Deployment History for the Orgs we have access to. Our clients brought this up as a concern during our deployment meetings.

When you Create a Scratch Org, the dialog that appears doesn't echo the DevHub name used to associate the scratch org. Since one's Gearset user account could be authorized to multiple DevHubs, one loses the thread (breadcrumb) to which DevHub is being used for the new scratch org

There is a new metadata type in API 48.0 NotificationTypeConfig. It would be great if you can add it.
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_notificationtypeconfig.htm

When a user might attempt to log into their account from a second computer (or VM), its appropriate to fail their login on the second computer. Right now, there is no indication that this has occurred because they're already logged in elsewhere. The error talks about adding Gearset IPs to Salesforce, but the issue is being logged in already.

I suggest telling us we're already logged in. It's easy to forget!

Thanks!

i would like to see the ability to filter deployments based on the components, just like the "Metadata comparison filter:" under Compare and Deploy option

I would like to be able to Clone a deployment and include all of the metadata from the cloned package, even if there are no changes in the target org. This way I can incrementally build up a master package that includes all my metadata regardless of where I chose to deploy it.

Currently, when cloning a deployment package or re-deploying a package to a new target, it only works with OAuth authenticated orgs. It would be nice to have more of my available saved orgs to be a target/source when cloning a deployment. I am not able to authenticate a target or source using a My Domain or Username/Password with this method.

Warn users when they are about to deploy (data OR metadata) to remind them when "Email Deliverability" is turned on.

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