It would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target.

It would be helpful if Gearset would notify the user when connection problems cause a monitoring job to fail.

For example, if the error "Error while getting access token due to expired access" occurs, Gearset could send an email to the author of the monitoring job informing them of the problem.

We need to set exact time for automatic deployment. We need this option for example for night releases for specific client. This is important for international clients that works in different time zones

I would like the ability to report on changes for an org over a time period grouped by metadata type or user. Filters would be by data, user, metadata type, change type. Would like to export or email the report too.

While this can be done with VSC custom plugins for SFDX, I think it would be really beneficial if Gearset offered the ability to sort Custom App XML in comparisons in order to see what's actually changing between a source and target for lightning page activations. Due to the way SFDC generates this XML, the way page activations are ordered is very difficult to follow, and I think it's an opportunity to make that easier especially for declarative config users of Salesforce.

If there are multiple users making changing the metadata in Salesforce and when one has to deploy their changes, it is not possible to pick the changes that are specific to one person, For this we have to go to VS code and use git patch mode to add only the necessary changes for a specific user. If we have an option to edit the xml after the comparision and pick only necessary pieces and deploy it to next org will save time and also switching between multiple orgs. Currently the comparison editor is read only mode.

Ability to Export Validated Packages from Grid, like Deployment History.

This feature would allow Enterprise user with Role"Owner" to Delete Validated Deployment by Other Users. The reason for doing this is that there could be packages created in error and this would allow release managers who are typically owners to cleanup.

This is a common issue with deploys from VCS to orgs and especially so for standard objects when SFDC introduces new versions and hence new objects

Example: In V53, SFDC introduced Standard Object "Customer"

If your VCS doesn't have a CustomObject for Customer and a Layout for Customer, the CI job will attempt to delete the Layout and get an error - you can't delete the only layout"

The Analyzer should detect this with recommendation to not delete; then CI jobs can honor this and not fail

If deploying from org->VCS and you get "Items requiring the master-detail field be added" - Gearset should look in the target and see if the various conditions (presence of master/detail fields/objects) already are present and avoid this analyzer message

Once your VCS is fleshed out, it will have all the custom object/fields you need and then from that time forward, this analyzer message is irrelevant/annoying.

Why should I see it every time I make any changes to the detail object for the rest of time?

If you clone a deployment, say from org to VCS, and you opt to create a branch as part of the dialog; the button to actually create the branch once you've named it requires scrolling to see.

It is too easy for the busy developer to miss this and just click the Run Comparison button - thus not actually creating the branch and doing the compare against the parent (wrong) branch.

The dialog should either resize, or be laid out differently - thus avoiding a potential disaster with the wrong branch updated (main instead of feature)

Deploy first fields where <trackHistory> was changed from true to false.
I am currently deploying fields changes and getting error that too many fields are tracked because fields with true ale deployed first.

Once you create a regex filter in your your Metadata Filter, you can't select it and edit it. You have to delete and re-enter.

This is especially useful when working with CI job filters

When you stop licensing a feature, there could be all sorts of cruft in the VCS that is otherwise challenging to remove using normal Gearset tools.

Example: We stopped licensing LiveAgent but our VCS is full of references to LiveChatTranscript and other CustomObjects used by this feature. This is particularly apparent with sub-elements of Profile

It would be cool if Gearset repo cleaner could detect when standard objects no longer available in the source org of the compare would be considered as deleted and all refs to those standard objects would be repo-cleaned.

We'd like the ability to view the number of changes that were deployed from the Deployment History table view so that we can quickly scan the list of recent deployments and identify certain deployments using that additional information.