When selecting "Select which tests to run" Gearset shows the tests included in the comparison first, but the moment all other tests are loaded, everything is selected.

When choosing this option, the tests included in the comparison should stay on top and selected, and the rest of the test should be added alphabetically but UNSELECTED.

If I'm choosing this option, I probably only want to run some tests. I think it would be much easier this way. Usually you need to run the tests included in the comparison and maybe one or two more.

When creating a new scratch org from either the Gearset UX or via a CI job, one often gets the Unknown Error message

Gearset should attempt to retry this error as often, a simple retry works. This is especially important for CI jobs which should not have to be attended to manually.

Of course, the better solution is to not get this error at all

I want to exclude outbound messages from workflows as we will have different urls in different sandboxes. Same with list views we want to exclude them from custom objects so that we can use CI using gearset for deployments

would be nice to have possibility to configure 1 source (git branch), but multiple targets (sandbox), so gearset would have some "load balancer", which would distribute the validations into sandboxes, which are not busy. Its taking too much time from developers to wait for their validations to finish.

I'd need an option to auto-deploy FLS for items i've selected in one click.
Sometimes the amount of changes is huge, and finding and clicking Permissions for selected items one by one is not a deal. For sure, it's possible to select all Permissions in Source org, and let the wizard to deselect Permissions for missing items in target, however that the result does not usually correspond to items that are in package.

create an option to have chained deployments so complex deployments can be broken down and sequentially deployed or slaves can be ran

allowing for multi staged deployments under one CI job

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.

When you are pushing a project with sfdx, there is no compare, sfdx just push the whole package.

It will save a lot of times.

After every release, we have to do smoke testing. We do have automated testing using selenium and we wanted to trigger the automated testing every after release is detected. It would be nice if in the deployment we can call an api or webservice after successful deployment. Or in the monitoring we can call an api when there's a change happened in the org.

Save draft deployment notes so when you combine drafts you can see all the notes from each single draft

On the "Summary of Items to deploy" page, the items in the deployment show in the 3rd column. So when you go to choose tests, you can't see what's in your package. Makes it very easy to miss a test.

Illustration: https://imgur.com/a/wbZOeiZ

I want to enforce that any deployment into a UAT sandbox runs all the tests. The standard Default option runs no tests since it's a sandbox. I have to manually choose the "Run Only my Tests" Option every time I deploy to that sandbox. I would like to be able to have that option selected by default

For every release, we have at least 700-1500 or more components to be deployed and adding all those one by one into gearset is a lot of manual effort which might sometimes not be entirely accurate. It would be great if there is an option where we can upload an excel or csv with all the component names and gearset would just create the package for you. It would save a lot of time and effort and reduce manual errors.

It's not convenient when a validation fails, to then download the excel file of the the validation errors, view in separately form Gearset, and then go through the list of metadata I'm trying to deploy and try to uncheck each one that failed the validation. It would be nice if Gearset did that for me.

Download the Gearset constructed package from CI job history when the CI job failed

Better error reporting when CI jobs fail. Many times I open a failed job and there are no errors reported.

Allow a basic find/replace to run against files before final deployment.
Examples: a username that would work in the sandbox that does not exist in production and we need to change it. Or deploying to a packaging org required a modification due to various namespace issues. Other tools have a means to do this in one way or another.

Is it possible to set time Instead of running CI Jobs every 4 hours or 24 hours.