Currently, a CI job that deploys from a Salesforce Org to another org or source control can only be scheduled to run at 4 hours intervals. Additionally, there is no mechanism of specifying when these jobs will run - instead, the job is scheduled randomly within the first 4 hours it was created and every 4 hours after that point.

Providing a smaller interval (ex. every 1hr) and/or more granular control over the job execution time seems like a common sense enhancement.

As of now we are able to send only static text as a part of outgoing payload in CI Integration jobs. We want this data to be dynamic for each deployment.
For example: We need to send the information like (JIRA User Story number, GIT commit hashes and descriptions from the pull requests being merged, etc.)
This will allow us to publish information of successful deployments to external system.

It would be great to refresh a specific item within a comparison that I know has changed since the last comparison.

Hi we use the data deployment feature is it possible to only select some fields to deploy data from one org to another and not always all the fields on an object.

Export the selected data source in a CSV file before deploying, in order to allow custom manipulation. Then allow the import of that CSV to destination - functioning like a more sophisticated Data loader.

In the past in Gearset, you were able to see the status of your deployment (e.g. 100/200 test classes, etc.) very similar to how you would see the native status tracker on the Deployment Status page within Salesforce Setup. It appears this feature is no longer available in Gearset and there is no status until the deployment complete. It would be great to bring this back to Gearset, so the tool provides the full deployment scope. Since this has been removed, I now have to open an additional page to monitor progress in Salesforce.

Allow gearset CI to do a quick deploy either by default or via a setting on the Job definition.
Our tests run for nearly 90 minutes and are currently run twice in succession causing a lot of frustration. Once when a PR is validated and then when it is merged and deployed.

1) Currently PBEs are incorrectly inserted with the company currency as apposed to the currency of the source record.

2) PBE's currency cannot be updated once created (SF restriction) but because PBE's should not be referenced by Id, (that would be a terrible design decision). It is quite possible to delete and recreate any out of sync records.

Ability to build sequence of data load (choose a list of data load templates and have to possibility to run them automatically in sequence). The sequence can be changed.

Giving team owners/leaders the ability to define sub groups of team members and control their ability to deploy to certain environments.
For example not being able to connect to/make deployments to 'production' orgs.

When entering test class names in the text field, invalid entries can be added without any indication that there is something wrong, which would lead to uncovered code and most likely a failed deployment. For example, entering in ThisIsAnInvalidTestName would not result in any error.

Sometimes there is a difference between a object because the order of the platformActionListItems are different. Sometimes an item with order 0 comes first, but it is possible that an item with 9 comes first. This is probably an error in Salesforce API, but Gearset should order this list before the comparison so 0 will always be the first item.

SFDC seems to retrieve the lead convert settings in non-deterministic order between orgs . Display only true changes/adds/deletes rather than differences in ordering of the mappings as they make no difference to the runtime execution of Lead Conversion

We can currently view deleted/removed data records in XML format as a list, but we can't export them into a CSV. This is necessary people who don't have access to Gearset and would be very helpful for users who have difficulty understanding XML.

It'd be great to see the "Friendly Name" in the Deployment Summary page.

e.g. https://app.gearset.com/finished?deploymentId=XXXXXXXXX

And to be able to add/edit the Friendly Name on that page, same as it can be done in the Deployment Summary.

Our use case: We audit all our deployments to make sure they have a name. It would be very helpful to be able to send a Deployment Summary link to a user to tell him to add a name if it's missing.

Currently outgoing webhooks support only basic authentication. It'd be useful to have oAuth support for outgoing webhooks for enhanced security.

if path contains "./force-app" a bug appears, if we write "force-app" it works. so first one should work to

Repro step :

{

"packageDirectories": [{

    "path": "./force-app",

    "default": true

}],

"namespace": "",

&quot;sfdcLoginUrl&quot;: &quot;<a rel="nofollow noreferrer" href="https://test.salesforce.com&quot;">https://test.salesforce.com&quot;</a>,

&quot;sourceApiVersion&quot;: &quot;48.0&quot;

}

Result :
Comparision failed

Expected Result:
Comparision Ok

If I need to find when a specific thing was changed in our system, my only option is either to use the last edited date or to manually check every daily comparison from Monitoring to see if it changed. Since many metadata types do not reliably update the last edited date, it makes it much harder to find those changes. If I could choose a specific metadata record and use that to search the Monitoring to see when it changed, it would be much easier to find it.