When searching on the comparison results screen the child items of an object are not part the search unless you expand the object.

If you expand and then collapse the object tree child items do then appear in the filter search. It appears to be just on initial loading that it doesn't work.

gearset doesn't seem to pickup date of change for custom field and custom metadata.

If you clone a deployment, say from org to VCS, and you opt to create a branch as part of the dialog; the button to actually create the branch once you've named it requires scrolling to see.

It is too easy for the busy developer to miss this and just click the Run Comparison button - thus not actually creating the branch and doing the compare against the parent (wrong) branch.

The dialog should either resize, or be laid out differently - thus avoiding a potential disaster with the wrong branch updated (main instead of feature)

Reading the previous suggestions this might be a bug.

Where a user has multiple connections to Github, Bitbucket etc. It would be good to be able to set a default connection.

It is suggested that when you go to Compare, the last selection should be displayed. But I am not seeing that happening?

I would expect the default Source to display, no matter what Compare I and setting.

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.

Usually a Metadata file retrieved from Salesforce starts like this:

<?xml version="1.0" encoding="UTF-8"?>
<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">

So two lines, first with the version and encoding UTF-8 and second with the type of metadata.

Now when GearSet does the deployment to version control, either from an Org or a Branch it uses this styling of the first row:

<?xml version="1.0" encoding="utf-8"?><PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">

So everything on one line, with the encoding in lower case.

I don't see a logical reason this should be different in the files and is then causing differences in the version control system.
Thanks for looking into this.

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": "",
"sfdcLoginUrl": "https://test.salesforce.com",
"sourceApiVersion": "48.0"
}

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.

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.