On the Test Monitoring Overview page; you should be able to see at a glance whether the test is running and how many methods have run vs total

Reason this comes up is if you establish a Unit Test run for your developer sandbox org, then you can't run (some) tests from your IDE against the same org "ALREADYINPROCESS Test already enqueued"

A quick glance at the Test Monitoring Overview would tell you if you need to wait 1 minute vs 20 - and guide your activities accordingly

The Selection count on ‘Compare and Deploy’ page doesn’t match with ‘Items Selected’ on ‘Draft Deployment’ when a draft deployment is opened. Having this in sync will help user that all selections are going in the deployment.

We need a lock to the custom comparison filters so that the team will be on the same page and only the deployment manager can be responsible for all the deployments

CI jobs use metadata API to deploy and run tests. The tests run serially. As such, CI jobs can take many minutes to execute

As an optional configuration for a CI job, and only if the CI is run against a non-PROD org...

1. Deploy metadata using Metadata API
2. Run tests using Tooling API (parallel testing)
3. If tests fail, use MetaData API to rollback the deployment

Ideally, this can shave off 50% of the CI job time

Add a button to start it immediately. Currently only solution is to change the executing time!

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).

The metadata API has a boolean option to "purge on delete", i.e. permanently erase deleted items rather than just moving them to the recycle bin. This option is not exposed in Gearset currently, but rather hardcoded to "false". For CI scenarios in particular, it would be extremely helpful to be able to specify that this option should be set to "true" for deployments.

E.g. If I generally want to include all Custom fields for all Objects in the comparison, but there’s one specific field that I don’t ever want to send across to the target org, it’ll keep popping up and I’ll have to uncheck it each time.

CI job that run all test takes ages. Can we use scrach orgs and test suites to run test in parelell in multiple orgs?
https://developer.salesforce.com/blogs/2018/06/running-tests-5x-faster-using-sfdx-and-heroku-ci.html

It would be nice to be able to see which items within a comparison are part of Draft Packages. We have a need to build multiple packages from a single Comparison of Instances. This can be done by creating many Drafts, but it is sometimes difficult to know if items have been added to a draft package already. If we could visually see this, it would allow us to generate and confirm our packages much faster.

I would really benefit from a dashboard option. A single place where I could see my CI Job history, Unit Testing Jobs and Monitoring/Backup history for all/a subset of my orgs.

I am using Gearset more and more to manage the state of my org's metadata, so it would be nice to be able to see it all in one place.

Should it be possible to set an equivalent of "friendly name" in Gearset but one that can also be spread to Saleforfce.

It would be useful to select all objects in the data deploy screen to make it faster to select a large number of objects (even better would be the ability to group objects and select whole groups at once)

Use case on Difference Viewer:

search on `profilerecordtypevisibility' (or use metadata filter and check Profile: Record Type Visibility)

Results
Unless the difference viewer already has the Profile(s) expanded for their components, you get no results

Desired behavior -- Search on components within Profile should show results; even if search takes longer

After setting up a CI job from a Salesforce sandbox to a Bitbucket repo, it looks like the CI job always runs a commit, even if there are no actual changes. It would be great to not have this happen to avoid having many commits where there are no actual changes.

Would like the ability to associate Jira tickets during the comparison process so that it can be saved to draft deployments and can continue to add as needed. Currently it appears you can only add Jira tickets after you have finalized all items for deployment.

Allow XML package for org snapshot/daily monitoring. This is to take the previous day's design to be downloaded in xml format that we can open in eclipse IDE.

The ability to use this product for CI/CD and various other use cases in the US federal space would be a huge win for many agencies. I know the FedRAMP process is quite arduous, but the contractual potential here is pretty massive.