Currently, you can create new filters in Compare & Deploy, but when you are comparing and deploying from within the Pipelines UI on your development org, you can only select existing ones. This either means you have to get your team to go into standard Compare & Deploy to set up specific filters first, or they always have to select the filter that includes everything.

Gearset is great for non-technical users or those that find Source Control daunting. However, the terminology used in Source Control has leaked over to Gearset, and I think this detracts from the useful aspects of it, and at times just makes it feel like an extension of Source Control.
e.g. "Create Pull Request" in the Pipeline UI should be labelled something more friendly like "Request Feature Deployment"

...support blank values and/or regex in the "Find What" field on Environment Variables.

I would like to replace the value in a field on a Custom Metadata Type with an environment specific value, regardless as to what the value is in the source file. Currently I need to specify an specific value in the source to be replaced.

Would like the possibly to set up a CI job that only syncs a sub-set of fields on a custom object. For example, we have an org to org sync where we want to update picklist fields but not autonumber fields. Currently we are running this job manually twice a day.

As a Salesforce implementation partner (SI) I have a lot of organizations to manage, well over 50. Each time a new org is added, I can go through and add all the users to that org, but whenever a new person is added to my team, I have to go through each connection and add that user to the list.

As the owner, I would also like to be able to see all the shared orgs inside my account, so I can centrally manage them, rather than just the ones that team members may have added.

We currently receive an email with deployment summary as PDF attachment after successful deployment, but we also want this feature for successful manual validation. This is help us review the validated package summary with Deployment approval teams in our ORG.

It would be great to have the capability to connect to more than one instance of Jira. We are switching to a different instance and we have to delete and recreated the Jira connections each time we switch instances.

I am managing a Gearset account and I need to be able to know who is using Gearset and who isn't so I can more properly assign licenses.

This might be an Enterprise feature, https://app.gearset.com/account/account-report, but really should just be something an account admin can run.

Hi team, not sure if there is a way to do that in the current setup, but I think it would be helpful to add the option to only notify the Pull-request creator/owner on the validation errors, instead of "hardcoding" the email recipients. Regards, Adrian

We have our GitHub PR settings set to only allow Squash and Merge for PRs because we want a clean history on the long-lived branches. It seems Gearset doesn't support this, when I attempt to promote it issues an error. This should be configurable or should detect this automatically from the settings.

Making a pull request via Gearset is only available from the Compare & Deploy Flow.

I'd the link to make a pull request available from deployment history so that users can make the pull request to the various Git/Salesforce environments.

Currently, I am telling my users to note the deployment id for their comparison and hit the link. This appears to work, but isn't user friendly.

https://app.gearset.com/finished?deploymentId={deploymentId}&notify=true

In the same way you enable Jest tests to run during deployment like that:
https://docs.gearset.com/en/articles/5204895-pilot-feature-source-control-setup-for-lwc-test-runs
We would need to run UTAM tests:
https://utam.dev/guide/introduction

Those are stored in utam folder and as sucha re not deployed to Salesforce org but rather "ran" by the test system.
UTAM is very similar to Jest but do a simulated browser test (including integrated services and login of users) that covers full scenario and several pages. It's possible by using Chromedriver through WebdriverIO. All these are nodejs libraries used by UTAM.

Precision Deployments for Layout is a great improvement, it would be great to have the same feature for other meta data, particularely for : Fields picklists, global value sets, List Views, Reports, Profiles, Permission Sets and why not Lightning Pages, now that the Dynamic Form is available for Acc, Contacts & Opp

We like that the Jira integration posts changes to the associated Jira ticket during a deployment, but we only want notifications for specific CI Jobs. For example we want our staging and prod deployments to post a notification in our Jira ticket, but not for other jobs such as back-deployments. Each post potentially emails Jira users and we want to limit these notifications. Currently the only work around is to remove the Jira ticket association from the PR in Gearset before promoting it, and this gets tedious if you have a lot of development orgs.