Help us improve Gearset

Welcome to the Gearset feedback forum. We love getting feedback from our users on how we can make Gearset even better.

Post your ideas and vote for others – let us know what’s important to you. We’re keen to hear about product improvements, new features, and bug fixes alike. We check this forum regularly and will keep ideas updated with their current status. If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Expose Salesforce Validation Errors within Github PR

    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…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. Add or ignore parts of XML after the comparison to ignore other users changes

    If there are multiple users making changing the metadata in Salesforce and when one has to deploy their changes, it is not possible to pick the changes that are specific to one person, For this we have to go to VS code and use git patch mode to add only the necessary changes for a specific user. If we have an option to edit the xml after the comparision and pick only necessary pieces and deploy it to next org will save time and also switching between multiple orgs. Currently the comparison editor is read only mode.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  3. Deploy first fields where <trackHistory> was changed from true to false.

    Deploy first fields where <trackHistory> was changed from true to false.
    I am currently deploying fields changes and getting error that too many fields are tracked because fields with true ale deployed first.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. Provide output from Gearset during the validation in terms of what tests were being run

    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…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  5. Option to have SCA results for last commit or Period, Instead of SCA for complete file

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

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  6. Offer the ability to set the ignorewarnings flag on an individual "Compare and Deploy" basis.

    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…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  7. Move Failed Tests before Passed Tests when deployment Fails

    Hi,

    I would love to see the Failed tests to be listed above the Passed tests in case deployment fails.

    Right now User has to always scroll down at the list (as you are usually not interested on what has Passed rather what Failed).

    Also this shouold be super simple to implement :)

    Thank you & keep up the good work,
    Cheers,
    O.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add Analyzer for "Cannot delete the only layout"

    This is a common issue with deploys from VCS to orgs and especially so for standard objects when SFDC introduces new versions and hence new objects

    Example: In V53, SFDC introduced Standard Object "Customer"

    If your VCS doesn't have a CustomObject for Customer and a Layout for Customer, the CI job will attempt to delete the Layout and get an error - you can't delete the only layout"

    The Analyzer should detect this with recommendation to not delete; then CI jobs can honor this and not fail

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow Package Version Mismatch Bypass for Org Deployments

    When deploying a branch to a Salesforce org where there is a managed package version mismatch in the file metadata, it would be nice to be able to bypass this discrepancy as there are occasions where there may be a newer package version in a lower/sandbox org and an older package version in a higher/production org.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  10. Warn on Master/Detail deployment even without comparing Custom Fields

    If you compare Custom Fields and try to deploy something in an Object that is in a Master/Detail relationship without including the Lookup field, Gearset will warn you that the deployment will fail.

    However, if you don't include "Custom Fields" in the comparison, (for example just comparing Validations) and try to push it, you will hit an error:

    "Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field"

    Gearset could easily warn the user on this when trying to push a Validation Rule on a MasterDetail object, even if Custom Field was not added to the comparison.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  11. Add Repo Cleaner support to SearchSettings

    When you delete a custom object, the Repo Cleaner should remove the references to that custom object in the Settings metadata type - specifically SearchSettings | <searchSettingsByObject>

    Otherwise, it becomes impossible to deploy Search Settings via CI jobs

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  12. Improve error message when XML is not properly escaped

    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…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  13. Display API name and friendly name of permissions within Analyzer messages

    when Gearset Analyzer tells you that you should consider removing a permission from the deployment, it displays the API name of the permission but often this doesn't tell you what item in the Setup UX you need to check on

    example:

    ContentHubUser is actually the permission for Files Connect Cloud My suggestion is that Gearset take advantage of this resource http://www.fishofprey.com/2020/10/mappings-between-salesforce-permission.html and display both the API name and the UX name in parens - such as :
    ContentHubUser (Files Connect Cloud)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add Analyzer to Warn/Remove Named Credentials with Passwords

    Currently, attempting to deploy a named credential will fail as a "password is required for the specified authentication protocol".

    This can mean manual work if you have a lot of CI deployment jobs to sandboxes or annoyance if you expected to be able to deploy it.

    It'd be great if an analyzer existed that would alert/warn the user about it going to fail and unable to be deployed (suggest removing it from the package)

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  15. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  16. Don't Delete Managed Package's object permissions from Permission Sets in CI jobs

    In a CI job, using source control as the source and including deleted items, you can run into an issue where objects from managed packages show as "deleted" in terms of custom object permissions from permission sets that have access to them. This can occur for permission sets designed to give access to managed package features or if you have a permission set with "View all data" or a system permission that gives them access to all objects in some capacity (read, write).

    Ideally, we wouldn't have to include managed package object permissions into Source Control (likewise, Gearset suggests only…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  17. Workflow failed to deploy without error, due to standard object dependency

    In a CI job : Validation shown as success & Deployment shown as success. But actually no workflow deployed due to it being removed in the Problem Analyser.

    The Problem Analyser triggered due to the (standard) object, that the workflow depends on, not being in the comparison results.

    In a traditional deployments object is not needed to deploy WF, that too standard object. I feel it is a gap - problem analysers should never fire on object dependency.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  18. Workflow failed to deploy without error, due to standard object dependency

    CI job : Validation shown as success & Deployment shown as success.. but actually no WF deployed. Saying Opportunity object doesn't exist in target just because it was not selected in the components. in a traditional deployments object is not needed to deploy WF, that too standard object. I feel it is a gap.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  19. Excluding Record Type Problem Analyzer Should Behave the Same Across Metadata (Layout Permissions, Custom Object Permissions)

    In the situation where a repository is the source and an org is the target, there may be a situation where a record type doesn't exist in the repository but references in the layout permissions and custom object permissions do still exist.

    Currently, the problem analyzer will catch the custom object permissions and ask you to remove the references to the record type that doesn't exist in the target.

    However, it doesn't catch the layout permissions and the deployment could fail with an invalid reference.

    In the absence of the record type in the repository, the "Problem Analyzer for excluding…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  20. Include Apex classes imported into LWC

    Ensure that Apex Classes imported in LWC javascript files are included in dependencies.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base