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

  2. Option to validate / deploy only running test classes in deployment set

    When deploying, there's a pain point when we want to specify tests to run. It would be nice to have an option to only run test classes that are included in the deployment. Automatically identifying which test classes are in the deployment package should be fairly straight forward:
    grep -ri @IsTest ./src/classes

    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

    3 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  3. Display which apex triggers have low code coverage if a deployment fails

    It would be great if Gearset can surface which Apex trigger has 0% code coverage when a deployment fails.

    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

    2 comments  ·  Testing  ·  Flag idea as inappropriate…  ·  Admin →
  4. Cancel deployment in progress

    In Salesforce, you can cancel a deployment in progress: Maybe because a test has failed already and you don't want to bother running the rest, or because you forgot some things.

    Can we have a cancel button while a deployment is in progress in Gearset? The metadata api seems to support it:

    https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_canceldeploy.htm

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow deployment of Sharing Rules by Rule not by Object

    In change sets we can pick individual sharing rules to push (specific ones on an object). However through gearset we can only push the whole object.

    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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  6. "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 →
  7. To add capability to mark (to ignore) not selected items to be able to remember that the particular item is not required to be deployed

    When compare source and target, sometimes u do an educated decision to NOT select something, and then selecting the rest of the items. Then if the compare results saved as a Draft Deployment, u may return back to it, and do a refresh for the comparison. In this case Gearset would kindly save all of the selected items. But for items that were not selected by the user, not they are mixed up with the new differences. So user have to remember, that this particular item he did not select intentinally, but this item that is not selected is a…

    8 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

  8. Select a set of data deployment templates and run them in order

    Ability to build sequence of data load (choose a list of data load templates and have to possibility to run them automatically in sequence). The sequence can be changed.

    8 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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Display Deployment Status Progress

    In the past in Gearset, you were able to see the status of your deployment (e.g. 100/200 test classes, etc.) very similar to how you would see the native status tracker on the Deployment Status page within Salesforce Setup. It appears this feature is no longer available in Gearset and there is no status until the deployment complete. It would be great to bring this back to Gearset, so the tool provides the full deployment scope. Since this has been removed, I now have to open an additional page to monitor progress in Salesforce.

    8 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  ·  Flag idea as inappropriate…  ·  Admin →
  10. More granular permission settings for sub groups of a large team

    Giving team owners/leaders the ability to define sub groups of team members and control their ability to deploy to certain environments.
    For example not being able to connect to/make deployments to 'production' orgs.

    8 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  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  11. Manage multiple Gearset teams from a single Gearset account

    I want to be able to Manage multiple Gearset teams from a single Gearset account, and not have to log out and log in again.

    8 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 →
  12. Provide ordering for metadata elements when committing to version control

    When metadata is retrieved from Salesforce the order of child nodes is not guaranteed and results in false-positive changes when committing to version control. Usually this will be something simple like workflow actions/criteria appearing out-of-order which can be compared manually. However, recently we've noticed entire profiles being committed with every permissions element out-of-order, resulting in a change set with ~20k lines where the actual change is impossible to visualize.

    Gearset should provide a feature to 'order' child XML elements alphabetically by name in order to provide consistent commits to version control and eliminate false-positives.

    8 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

  13. Set time on CI Jobs instead of running every 4 hours or 24 hours

    Is it possible to set time Instead of running CI Jobs every 4 hours or 24 hours.

    8 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 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow deployment of unlocked packages

    At the moment, you can select "Installed package" as a metadata type to compare, and I think you can use this to install a package (without installation key).

    However, unless I'm missing them, 2nd Generation Unlocked packages don't appear in a comparison like this.

    It would be really useful to be able to deploy 2GP with Gearset because I sometimes need to make metadata changes at the same time as installing

    e.g. I'm moving some old functionality into an Unlocked package and that old code has logic in the triggers. I want to be able to delete the old triggers…

    8 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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add Upload CSV functionality to create an upload template for CPQ deployments

    For CPQ Deployments add an "Upload from CSV" feature where a user could upload a file with specific External IDs across multiple objects to tell Gearset what to migrate in a single click.

    For example, the user could list the Object API name in Column A of the sheet and the External ID in column B and then Gearset would parse this and create a Data Deployment based off of those records specifically. This would be incredibly useful for any CPQ deployment where you need to only deploy specific records not the entire object!

    8 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 →
  16. Schedule data deployments

    The current data deployment functionality works fine for one-off deployments, but if you are trying to keep specific data in sync across multiple orgs, the ability to schedule data deployments for a given time in the future would let you deploy on a recurring basis automatically. Becomes especially helpful when combined with the current data filtering options.

    8 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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Offer to push components that passed validation even if some items failed

    For large payloads (thousands of artifacts) it can be tedious to try to resolve a few minor issues when 99% of the package will deploy successfully. Having a feature to push stuff that passes validation would be helpful. Included in this in the deployment summary and deployment reports will be a count and list of items that failed validation and were omitted from the package so they can be investigated

    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

  18. Scheduled deployment freezes

    Prevent deployments during certain periods of time for a team or for production environments

    8 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 →
  19. Allow comparisons of a single commit from a VCS

    Currently, you can select a VCS repo and branch to use for comparison. It'd be great if you could select a specific commit from that branch, so that you're only looking at an atomic set of changes. This would allow for fine-grained comparison and deployment of changes.

    8 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

  20. Provide an API for querying deployment info

    Please provide an API for querying deployment info such as friendly names, components, deployment notes, etc...

    8 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 →
  • Don't see your idea?

Feedback and Knowledge Base