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. 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 →
  2. gearset doesn't seem to pickup date of change for custom field and custom metadata.

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

    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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 →
  4. create a Default Value setting on Source Control & Connections

    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.

    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 →
  5. Gearset silently removes SocialPost Layout Permission when deploying

    When deploying from one org to a git repo (or other org) and selecting Layout + Profiles gearset will display a Layout Permission for the "SocialPost" object. However when completing the deployment "SocialPost Layout Permission" is removed because deploying it would cause Salesforce validation errors. This is not displayed anywhere and always causes "SocialPost Layout Permission" to show as "New" when doing a 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

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 →
  7. Problem Analyzers don't evaluate changes made from other Problem Analzyers

    Even though this example has an easy workaround, it does seem like a scenario which could present issues in other deployments.

    In the scenario where a standard application that doesn't exist in the target (ex. Sandboxes and LightningInstrumentation) is included in a deployment (along with its permissions), there's 2 problem analyzers that come into play

    1. "Remove standard application additions/deletions from deployment"

    2. "Remove items which reference the listed components which are not available in the target"

    When both metadata types are selected (application and permission) only #1 is flagged. This means Gearset removes the standardApplication, but leaves the references to the…

    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 →
  8. Retain source control branch selection when cancelling a comparison

    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.

    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 →
  9. 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 →
  10. 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. 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 →
  12. 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 →
  13. 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 →
  14. "Next" button on comparison page sometimes does not work

    Sometimes, the "Next" button on the comparison page does not work. In the Developer Console I can see a 403 response from "POST https://app.gearset.com/api/static-code-analysis", traced to "raygun.js:2016".

    In this case, I have to reload the comparison page.

    This happens quite often (I estimate 1 in 5 times).

    I don't think that it's a timeout issue (CSRF token or sth.), because just right now I only marked one file in the comparison list and wanted to proceed, and the button didn't work.

    On other occasions, I spend a lot more minutes on the comparison page, and the button works perfectly.

    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 →
  15. Add new connection ends in loop

    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)

    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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. Changed by and Changed Date not populating from DX structure in Repository

    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.

    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