When trying to gather packages together to combine them for a release, currently it is not possible to first limit by a text search then expand the date range (search hangs due to number of retrievals)

Could there be a way to enhance the history search to enable easier searching?

When looking at a comparison it shows changed by as a column, would be helpful for consultants to Show Created By and Created Date as well

The drop down lists for picking source/destination are different in the UI.

For example, in compare and deploy production salesforce connections are not in the list alphanumerically, they are appended to the bottom while in a clone deployment they are all listed alphanumerically.

Just being picky, but consistency one way or another would be great.

The issue is, when promoting from one org to another and changing either Custom Object Permissions or Custom Field Permissions and if more than the profile you want has been changed, the extra profile changes get promoted anyway. So we need a way to control which profiles get applied when promoting field and object level security.

I'd like to be able to export a snapshot of all the metadata from my production org (include all components) to my git repository by clicking a single button.

After every release, it's worth taking whole metadata export from the org to git for the next/on-going releases.

For now, we have to create a couple of metadata projects to export the metadata to git, which is a tedious job and takes a lot of time.

Creating a visualization of the DevOps process removes the need for separate Visio diagrams or visual aids to represent the process. Also by creating this feature, you could allow for a drag and drop type feeling to represent CI Jobs, Data Deployments, Comparisons, etc. Users who may be new to a DevOps environment would pick up the process quicker allowing them to quickly adapt to the tools and this type of deployment mentality.

it would be good if we can send email notification to Users whenever we successfully deploy components to specific Org regardless of CI job.

I'd love to be able to have an extra "warning" message when targeting certain orgs when clicking the "Deploy" button. The thought is that it provides an extra level of confirmation when targeting production, to help avoid mistakes. This could be an optional custom warning message set on a connection that if populated, a "Deployment Confirmation Message" is shown.

In the new UI for Validation to view failed test classes error messages you must click into each failed class to view the details.

The previous UI showed "part" of the error message within the table. This was extremely useful in identifying all of the "unique" errors that are occurring.

IE: If 58 test classes fail from "4" unique issues -- then in order to determine that you may need to click into all 58 test classes or fix one at a time --> refresh --> validate.

This is just a time save feature.

When you clone a deployment package you have to select your Source details, but the selections do not default to the the last used settings or to a recently/commonly used settings. This is a minor annoyance but in other parts of GS you have the last selected options already selected based on user history, so hoping you can extend this to the Clone page

Agile/sprint planning tool similar to JIRA

When deploying code, it would be nice to have an option of having an exclusion list of test classes to not run.

For example; when adding new custom fields, you generally have to add the permissions as an additional line item to the deployment. Having a checkbox or something that will have gearset automatically add the permissions associated with the metadata currently in the deployment list would speed up the process. Users should also be allowed to deselect lines that were automatically added.

It would be cool if the custom deployment configuration could be driven from a Pull Request . For example, in GitHub, the Pull Request knows which files were changed and approved. Why not use that list to instantly populate a comparison to create a deployable manifest to go from source control to org?

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