When creating a new scratch org you have the option of specifying the package and the installation key. This option is not available in a CI job to scratch org target scenario.

When there are dependencies specified in the sfdx-project.json file that requires an installation key the CI job run fails when the CI tries to install them.

There needs to be a way to specify the installation key, either by a custom JSON field in the sfdx-project.json, or on the CI job itself.

If you click "compare now" and then click "cancel" before it finishes, the "compare metadata" screen retains your selection for orgs, but does not retain the branch selection for source control.

It defaults to the first branch by alphabetical order versus what I selected before I cancelled. This can cause confusion for users who do not notice.

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 we replace default DataSet in Einstein Analytics, it creates another type of metadata "WaveXmd". Support for the deployment of this metadata is missing from Gearset and as per discussion with Gearset team, it's a bug. Could you please fix it.

When choosing specified tests to do a validation, let's say from a comparison that was created from a bunch of drafts that were combined, the pop-up will show the specified tests that were chosen originally for those drafts that were combined. That is awesome and is exactly what I want.

The problem is the "Fetching test classes from Salesforce" then occurs automatically and replaces that list with the full list of test classes, and check the boxes for all of them, replacing my existing list. That means I have to go back and choose my list of specified tests again.

When I add a new connection via choosing "Salesforce authentication", I need to enter the username. I click on "Authorize". Instead of a redirect to the Salesforce login screen, I see a blank page with a gearset spinner logo. But this screen takes hours and will not redirect. I'm using Firefox and the Org is a sandbox (sandbox is also selected)

After doing a major changes in an org, one can be left with a lot of deleted components to deploy. In the comparison view, they don't show up as expected. The Changed On" date isn't the date deleted. It uses the last modified date in the destination. So deleted something last week could up as last modified 2 years ago.
Ideal: Gearset would to get the Setup Audit Trail via API and display the actual deleted date of deleted components

At commit to branch, Gearset reorders large chunks of the XML file. This causes additional deltas (seen in the hundreds of lines) and merge conflicts.

When deploying a permission set, it was being deployed without the permissions checked, even though Gearset detects that the permission is checked in the metadata compare.

Using the DX/source structure in a repository (Github), no "item changed" date is shown for any metadata types in the comparison window.

This leads to gearset not being able to provide last changed date or who last changed anything in a Source DX repository. It's left with "unknown" and makes our comparisons and selections more difficult when users rely on that information.

The custom object translation of the Product2 object, specifically, is not behaving like the other custom object translations. So when I changed the label of this standard Object : Product2 (Set-up -> rename tabs and labels)
i can't find it in Gearset. I have to make this change manuelly.

When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.

We did a deployment last week and noticed that as part of the deployment report that went out that it stated the Tests Run was zero. We did a pre-validation the day before where we ran all tests with all passing.

Could this test section on the deployment report again include/include the pre-validation tests that were run for the deployment?

We have no way of knowing when the files were last changed on the source control side. Tried only with BitBucket though.