If you deploy Custom Field Permissions for fields such as Task.ActivityDate or Task.WhatId to a Permission Set, the Gearset Analyzer auto-checks Do Not Deploy and shows this message: "Some field permissions in the deployment are for fields that Gearset thinks are required fields on the target side. Field permissions cannot be set for required fields."

While this is a useful message when deploying Custom Field Permissions to a Profile, it is not a useful message when deploying to a Permission Set as that Permission Set might be used in conjunction with Profile "Minimum Access - Salesforce". If you are using Pipelines, then the CI job will automatically exclude these deployment items unless you create a custom Problem Analyzer set. It can take considerable debugging to even realize this has happened when your UAT starts failing in weird ways when dev was just fine

Currently when a PR Validation fails (Deploy CI Job with Validate Target setting turned on), the user can click the Gearset "Details" link to go into Gearset to see the exact error.

Many of our devs use VS Code and Github for their daily work and only rely on Gearset for the CI job. Having them jump into Gearset just to see the error is time consuming and not very intuitive for them. Sure we can find the same errors within the target org of the CI, but at that point the list of validations is large and it's hard to find.

If we could have the CI job trigger a comment on the PR of the Success or Failure (with errors or at least first 10 errors) then our developers could have a smoother time staying within Github.

Suggestion
In "Problem Analysis" page, the problems indicated and solutions are not necessarily obvious and understandable.

The suggestion to read more about the analysers in the user guide is in the case I'm facing an enormous challenge.

Copy and paste the problem into your search mechanism brings back endless answers - not one used the wording in the problem statement!.

Here's an idea, have a button/link with each problem that take one to the user guide section (or other documentation) exploring the problem.

No hunting for answers as the 1st choice to figure out what your product is saying. It's now the 2nd choice.

The first is documentation that delves into what the problem/solution is about.

The devs caught this problem, the devs indicated through a sentence or two what problem was caught.

Provide a starting point, a well documented starting point.

Would like to see the ability to set the IgnoreWarnings as an override for an individual Compare and deploy, in addition to at the global level. Occasionally, we will do a community deploy, for example, that returns a warning about a page that includes a Dashboard component, with the warning that the Dashboard ID or the Filter ID might not exist in the target environment. Once we see those errors in the validation results, it would be convenient to rerun the deploy, and ignore those warnings. Possibly similar to how the Test execution options are set on the Deploy button dropdown menu.

I had unit testing jobs running ALL tests in source (full sandbox) and target (production) org - resulting in 80% and 79% test coverage. However, when I started to deploy my changes - the validation failed because test coverage was only 74%. Finally, after a few days, I figured it out.

I was just simply clicking "Validate" (i.e., did not choose specific tests). In the past - that ran "all tests". But something seems to have changed. When I picked "choose tests", about half the tests in my org were "automatically selected". I manually selected all other tests - effectively forcing all tests to run. This time the validation passed!

It would be great if there was some output from Gearset during the validation in terms of what tests were being run (partial vs all)

Hi All,

We are looking for a SCA feature so that instead of showing all the errors and warning in the whole file while doing compare or deploy, It Should only show the SCA errors and warning for the last commit or for commits during an specific time interval.

For Example I have an existing Apex class which is having 1000 lines of code and say 100 errors are there as per GS SCA analysis. Now let’s assume I am working on that file for my current sprint and I am adding another 100 lines of code in that class. Now after doing the compare and deploy the SCA should give me the errors and warning for the latest 100 lines of code and not for the complete file.

Regards
Shahnawaz

When I choose to compare metadata with my source as my VCS, there was an "&" char in the recordtype XML definition file.

    <values>
        <fullName>Food & Beverage</fullName>
        <default>false</default>
    </values>

This threw an error and there was no support and no explanation at that time.

I suggest you to improve this error message.
Message I got:

Could not parse the XML for 'force-app/main/default/objects/Lead/businessProcesses/Buyer.recordType-meta.xml'. Error occurred at line 71. Further details: An error occurred while parsing EntityName. Line 71, position 29.

File, line and position it's ok. maybe a link to Gearset docs with walkthrough with this probable cause when a parsing error happens.