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. Stop the reordering of XML when deploying to git

    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.

    22 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 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  2. "Changed on" date on source control side of comparison does not show

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

    9 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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  3. Keep list of specified tests

    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.

    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

    2 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  4. Scratch orgs with packages with InstallationKeys fails to install in CI

    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.

    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

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  5. When Field is Deleted Permission Set changes are not recognized for the Field

    Let's say we have only one object in the system. Addressc. And we have one Permission Set -> "System Administrator" with only "FieldPermissions" for all fields in the "Addressc" object.

    Now I wish to Remove 2 Fields from "FieldPermissions" of the "System Administrator" Permission Set.

    1st Field I'm removing just because I do not want the permission to be in the Permission set
    2d Field I'm Removing from Permission Set, as I have physically deleted the Field.

    On Compare And Deploy Page I will See Deleted Field and I will see only one Section to be removed from…

    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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  6. When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist

    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.

    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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  7. 3 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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  8. For Deleted components, "Changed On" date should be date component was Deleted

    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

    3 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

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  9. Permission sets not deploying correctly

    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.

    3 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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  10. Suppress "changed on" datetimes in difference viewer where datetime is the same as the metadata retrieval datetime

    The difference viewer will show Changed on values for the current datetime for certain metadata types - probably because SFDC is returning such a value when, in fact, the source didn't change at all

    • Custom object
    • Settings
    • Standard valueset
    • Workflow rules

    displaying the current datetime of the compare run (i.e. the metadata retrieve datetime) is not helpful when trying to filter on changed date in the difference viewer (i.e. sort descending)

    3 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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  11. Deployment of pre-valided package doesn't include accurate test counts

    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?

    3 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

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  12. False positives in managed code

    When I enable comparing managed packages (e.g. when I have added a field to a managed custom object), I get lots of false positives saying that there are differences in apex code.

    On the source org, the code is show as "(hidden)"; on the target it is shown as empty. And Gearset lists this as a change.

    Obviously, I know it's not a change, but it adds a lot of clutter to the comparison view.

    3 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 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  13. Deploying from SF to Repo with unlocked packages can result in items deploying incorrectly

    When deploying from SF to a branch that has the force-app and unlocked packages, if you deploy an item that would include the object file it deploys to the unlocked package directory instead of the default app listed in the project.json. The end result is everything related to the object is moved from the force-app to the unlocked package directory.

    Steps to recreate:
    Enable source tracked sandboxes
    Create a new dev sandbox
    Create a new branch and link it to the new sandbox
    Create a new field on Contact
    Edit a search layout on Contact
    Use gearset to deploy the…

    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

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support for WaveXmd metadata is missing

    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.

    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

    Started  ·  0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow standard linux path in sfdx-project.json

    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

    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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  16. Don't change the first 2 rows of a metadata file in version control

    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.

    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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  17. Include a field's permission if the field is flagged as a missing dependent component

    If a field is identified as missing from the deployment and the user agrees to include it, the corresponding field's permission should also be added.

    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

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  18. Page Layout Deletion Not Detected

    When I remove a page layout from my Git repository (the file and the package.xml entry) and then do a comparison to an org that it still exists in, Gearset fails to detect a deletion. It doesn't even show up in the All objects tab. It happened to me yesterday and then I just reproduced it now.

    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

    2 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  19. The number of differences does not appear to the left of the Prev/Next buttons in XML view mode

    However, the number of differences does appear when viewing the same Apex class in APEX view 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

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  20. clone deployment dialog is too small vertically when adding a branch; leads to mistakes

    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)

    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  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base