Edit "Existing Saved Filters" on an "Existing CI Job"

If using a saved filter on CI job, there is no easy to update an existing saved filter from the CI job directly.

Create a mechanism by which CI and CV jobs can be archived, but not deleted. Sometimes there is a job that is not used, but the history needs to be kept for some period of time.

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

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

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.

I am able to deploy profile components and permission sets separately. But the permission set assignment is part of salesforce SOAP API and I couldn't deploy the same using GearSet.
Kindly provide deployment options not only for Metadata API, also SOAP APIs

This will allow to deploy Case.settings without getting this deploy error:
EmailToCaseRoutingAddress[Info]: emailServicesAddress is a read only field and cannot be changed

List deployments resulting from a CI job on the Deployment History tab along with manual deployments.

We currently deploy metadata using both manual and CI jobs and it would be convenient to see all deployments in the same list (for debugging, reporting, monitoring).

Can you create a master-switch deployment option? It would be similar to how this operates: https://sfswitch.herokuapp.com/

The issue is that this master switch does not always work with managed packages in production orgs.

So a way to automate the turning off/on of Validation Rules, Process Builders, Flows, and Triggers.

Use Case: We are building a new app and have significant data migration to do. It would help to have a master switch to turn off processes in PROD, deploy date, then, flip the master switch back to turning processes back on.

UX suggestion:
On the CI jobs page...

Currently - you see last run dateTime followed by "deploying...." if a job is currently in progress

Suggestion: Add the dateTime when job started so user can gauge when job should finish and set expectations accordingly

For example, in our shop, a CI job should take around 20 minutes - but if you can;t tell when it started, you can't gauge when it will finish and plan your work accordingly

Please set it so that we can force a code coverage check on deployments (including CI). I'd like to verify on the lowers before going through to production. Might be able to do this with test cases but should be able to on deployment.

In Chrome, it is possible to display info even when viewing a different tab.

For example, I see this done with financial sites when they want to show the value of a stock ticker symbol.

Hello,

It would be very nice to be able to have a test classes suggestion when doing a deployment with "specified test level". The suggestion will ensure the package elements will be covered at least by 75% and so speed up the deployment.

Allow Deployment Notes to be editable post-deployment. Our team uses very specific notes for auditing purposes, and being able to edit them post-deployment would make that process a lot easier for our teams.

In the CI job, we would like to have the ability to specify on a metadata level if we want to deploy new items, update items and delete items. There are examples of metadata where we always want to delete and others where we don't want to.