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. Implement public key authentication for source control

    Implement public key authentication for source control.

    Allow Gearset to generate a public/private key pair, and expose the public key for use in authentication to source control.

    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

  2. Extend Jira Cloud Integration to Releases and Bitbucket

    We do the majority of our management via Jira and have it linked to Bitbucket and our test system so that we can manage everything via Jira. It would be great to extend the current integrations to more intelligently link the package to Jira tickets and the corresponding Bitbucket code and then push back to Jira the deployments in a more Jira friendly manner e.g. potentially creating/updating a Jira release for the deployment.

    4 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. Create a Master-Switch Only deployment process

    Can you create a master-switch deployment option? It would be similar to how this operates: https://sfswitch.herokuapp.com/

    The issue is that this master switch does not always work with managed packages in production orgs.

    So a way to automate the turning off/on of Validation Rules, Process Builders, Flows, and Triggers.

    Use Case: We are building a new app and have significant data migration to do. It would help to have a master switch to turn off processes in PROD, deploy date, then, flip the master switch back to turning processes back on.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  4. Adjust dependancy on managed package versions for Apex[Class|Page]

    We've found when developing classes against managed packages the class ...meta.xml includes the package version numbers. Problem is these are fixed to the exact version installed (e.g. 9.4, 9.3 etc. example below)

    But then if the managed package is upgraded Salesforce, in its infinite wisdom, doesn't update these so when you come to deploy next time you have to go and manually update all the version numbers - or if you have a different version in another sandbox (to test the newer one) same thing.

    Seems like something a cool deployment tool could handle and offer to fix up on…

    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

  5. Restrict source orgs

    For example, deployments to a production environment should only come from the master branch of our git repository

    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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  6. I have so many connections and jobs, is it possible to have group them (in future release?)

    I have so many connections and jobs, is it possible to have group them (in future release?)

    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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  7. Trust Site

    Right now, Gearset is down and we cannot use it. It would be good to have a trust.gearset.com site that shows what is going on and what the team does to fix 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

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  8. would be cool to be able to "ignore" certain differences

    would be cool to be able to "ignore" certain differences... e.g. encryption. So if encryption is enabled in a Production Org but not in a Sandbox (not sure if Encryption is possible for SBs), you have a difference for every custom field <encrypted>true/false</encrypted> which is really irritating.

    11 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

  9. Allows admins to limit the available branches of a repository

    When connecting a source code control system, quite often an integration user account is used that may also be used for other parts of the enterprise. Please allow admins to restrict the available repositories and branches so that users can only run comparisons for the branches they should actually have access to.

    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  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Improve PermissionSet comparisons by providing an option to ignore fieldPermissions when their editable/readable are set to false

    Current Metadata Behavior:
    When a new object is added, objectPermissions are only added to a PermissionSet only if one of allowCreate, allowDelete, allowEdit, modifyAllRecords, viewAllRecords are set to true
    When a new field is added, the new fieldPermission is added to all PermissionSets by default (with editable and readable set to false).

    NB. PermissionSets are additive in behavior and can only open up access not revoke. Values of false have no meaning and are only noise.

    Current Gearset Comparison Behavior:
    Comparing PermissionSets show these new fieldPermssions as New Items even when default values for editable, readable are set to false.…

    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

  11. Add deployment support for Macros

    Macros deserve to be added to source control yet there is no way to do this with Gearset:

    1) Data feature (paid add-on) doesn't deploy to/from source
    2) PRO/Enterprise can't source/target deploy Macros because it is not available with the Metadata API.

    Since macros represent some debugged logic, managing in source control makes sense. Curiously, SFDC has chosen to make Documents available via Metadata API but not Macros

    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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add an auto-save feature while building deployment packages

    As Gearset is run through a web browser, if the browser happens to freeze while a package is being built, you don't have the opportunity to save it as a Draft Deployment. An auto-save feature would allow someone to pick up where they left off, or when the last auto-save was done, without having to start from scratch.

    45 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

    7 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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

  14. Allow for selecting which repositories to display for github in org settings.

    It would be helpful to be able to select repositories to display in the selection under Manage Orgs. Some of our repos in Github aren't related to Salesforce deployments, and filtering those out so they don't even show in the list would be really helpful in getting to selections faster.

    11 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. Ability to manually hide/filter component differences by single flag

    When reviewing comparisons it would be extremely helpful to have the ability to manually 'hide' a component difference (e.g. a single flag to filter out, ignore, or even 'grey' a component differences) once you have a) reviewed the XML and b) determined you do not want to deploy or view that component in a saved draft. I.e. a third state that is not simply 'selected' or 'deselected'.

    Current filters by component type, name, et al. don't accommodate for wanting to hide a known component difference (e.g. like an Apex class still under development) so that you can only see remaining…

    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

  16. Reuse Deployment Package (clone) should use sticky "Source Repository"

    Use case:
    1. Compare and deploy from repo-R/master to org A
    2. Clone deployment from repo-R/master to org B

    Unfortunately, when the clone deployment displays the dialog "Reuse Deployment Package"...

    a) When you select GitHub, the dialog doesn't default the repository to Repo-R but instead displays a picklist of all possible repos the running user has access to (in our case that is 100+)
    b) Better would be to remember in cookie the repo the developer last used and default to that choice so scrolling through 100 items is not necessary.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  17. Show # differences found in comparison display

    It would be a nice feature to see the number of differences for each item from the perspective of the source org vs target org.

    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

  18. When a Picklist Populates, Don't Default to the 1st Value, Default to Blank

    When I choose my destination, the system defaults the picklist to the first item on the list. Instead it should populate the list but don't pick a value.

    For example, when I choose destination = BitBucket, it then takes a moment to load available branches. It takes a little bit so I go on and start to configure the metadata types. Meanwhile, Gearset populates the list and sets the value to the 1st branch on the list, in my case, feature/helpdesk. It should leave the value blank and make me pick.

    This has resulted in me running long-running comparisons, and…

    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

  19. Be able to switch the direction of a comparison/deployment

    Sometimes we need to reconcile changes on an object between two orgs, where some of the changes have been made in Org1 and some in Org2. Having set up metadata filters, compared and deployed required changes from Org1 to Org2, it would be nice to be able click a button to switch direction to then deploy required changes from Org2 back to Org1, without having to go through the whole process of setting up a new comparison.

    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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  20. CI job status "deploying" - add dateTime

    UX suggestion:
    On the CI jobs page...

    Currently - you see last run dateTime followed by "deploying...." if a job is currently in progress

    Suggestion: Add the dateTime when job started so user can gauge when job should finish and set expectations accordingly

    For example, in our shop, a CI job should take around 20 minutes - but if you can;t tell when it started, you can't gauge when it will finish and plan your work accordingly

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base