Quite often an Environment needs to be refreshed, but every time it happens all the integration breaks as OrgId changes. Gearset can move metadata and data, which when made together can be a solution for sandbox refresh. Full copy sandbox sometimes takes days, GS will be able to it quite quickly.

When working inside of Gearset, it often alerts you to changes that have been recently made. It would be nice to have these as a separate, consumable, feed. We have a slack channel that we would like to pipe those changes to, for instance.

This would be handy:

If you have a CI job (deploy type) with various configuration (metadata filter, notification, etc) and you want to Duplicate that job, you can't duplicate it to a Validation-Only job. You have to re-enter everything.

I think it will be very helpful to have a possibility to deploy only some selected changes in the modified component.

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?

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

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.

Agile/sprint planning tool similar to JIRA

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

It will be helpful if we know who/when a filter is changed. And it would be great if we could lock the filters as an owner.

In rarer situations where I need to make some manual adjustments to the metadata XML for a deployment, I'd like to be able to download the metadata to adjust it. Today you need to go through a compare, and at the end, you can download the package, but this can be problematic, since you have to choose the target org, there need to be differences, etc.

Instead, it would be useful to just choose the source org, select the metadata items, and save the package, without a target org needed.

Similar to "Pending Deployments" It would be nice to see pending validations. We have several users in gearset, so if we are trying to validate something while someone has already initiated a validation, we receive the error that set up has been locked. So prior to validating a package, it would be great to check if anyone is in the process.