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. Show *all* matching items on All Items, even if they haven't been changed.

    I couldn't find a field that I was looking for today, despite searching for it specifically, because it was hidden inside it's parent object. I understand that the reason for this was something to do with there being no difference on the field (and I appreciate that the reason is to avoid clogging up the screen!), but if you're searching for a specific field, I think it should really show up...

    Took me bothering someone on live chat to figure out what was going on.

    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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  2. Selection Count Mismatch

    The Selection count on ‘Compare and Deploy’ page doesn’t match with ‘Items Selected’ on ‘Draft Deployment’ when a draft deployment is opened. Having this in sync will help user that all selections are going in the deployment.

    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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  3. Need a Lock to the Custom comparison filters

    We need a lock to the custom comparison filters so that the team will be on the same page and only the deployment manager can be responsible for all the deployments

    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

  4. Be able to exclude single items from comparison

    E.g. If I generally want to include all Custom fields for all Objects in the comparison, but there’s one specific field that I don’t ever want to send across to the target org, it’ll keep popping up and I’ll have to uncheck it each time.

    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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  5. Track Items Added to Draft Packages

    It would be nice to be able to see which items within a comparison are part of Draft Packages. We have a need to build multiple packages from a single Comparison of Instances. This can be done by creating many Drafts, but it is sometimes difficult to know if items have been added to a draft package already. If we could visually see this, it would allow us to generate and confirm our packages much faster.

    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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  6. Filter on selected items

    I want to quickly be able to identify components that have not been reviewed by only seeing unselected items in the "Changed items", "New items" and "Deleted items" top level filters.

    seeing the ones I have already selected slows down productivity and I have to scroll through them. If I want to see them I can always look at the "All items" section. This information is also available in the difference type column.

    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

  7. Search for components within Profile should show results regardless of expansion of specific profiles

    Use case on Difference Viewer:

    search on `profilerecordtypevisibility' (or use metadata filter and check Profile: Record Type Visibility)

    Results
    Unless the difference viewer already has the Profile(s) expanded for their components, you get no results

    Desired behavior -- Search on components within Profile should show results; even if search takes longer

    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

  8. Allow XML package for org snapshot/daily monitoring

    Allow XML package for org snapshot/daily monitoring. This is to take the previous day's design to be downloaded in xml format that we can open in eclipse IDE.

    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

  9. Difference Viewer custom object name: include suffix __c, __x, __mdt, __e, etc

    When you look in the Difference Viewer, it is not clear at all by inspection which line of Metadata Type "Custom Object" is a standard object, custom object, platform event, custom metadata type, historcial trending object, etc.

    For example, Custom object Foo__c displays simply in the Name column as Foo. This is a loss of information in the difference viewer, especially if one has similarly-named custom object metadata types such as:

    Fooc
    Foos
    e
    FooConfig__mdt

    these display as
    Foo
    Foos
    FooConfig

    The full Sobject Name gives the user hints as to perhaps other related components that need to be…

    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

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

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

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

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

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

  15. Show filtered counts on the results grid tab titles

    When comparing two orgs. We need to show the eaxact number in the Tabs(Changed Items, New Items) when filtered.

    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. Display "Metadata comparison (custom) filter" used on "Comparison in progress" -screen

    Hi! I just started to evaluate Gearset. Looking good. When I was staring at "Comparison in progress"-screen this came to my mind:

    Sometimes it takes a bit longer than expected and I start to think: "OMG - What custom filter I used? - Probably I'm comparing everything - That's why it takes so long - Maybe I should cancel this job?".

    It would be more reassuring if the Metadata comparison (custom) filter being used was also shown on that "Comparison in progress" screen.

    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

  17. Simple visualization showing Process Builder differences

    Assuming the high-vote count Idea for matching on latest version Process Builder flow between source and target (and not by version #) is implemented; make the visual comparison between source/target PB not solely XML.

    Process Builder in XML can't be deciphered by a human mind. Hence, a simple indented text-based visualization could be done to make it more readable

    1. Decision 1.1 Entry criteria 1.2 Immediate actions 1.2.1 action 1 details (XML here OK) 1.2.2 action 2 " " 1.3 Scheduled actions 1.3.1 scheduled action 1 (XML here OK) ...
    2. Next decision ...

    There's an implicit tree layout in the PB…

    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. refresh comparison UX - echo the filter used in the original comparison

    When you click Refresh Comparison, the dialog does not echo anywhere the original filter name used in the comparison-being-refreshed. You just get a x/y filters being used.

    Always good to remind the user as to which filters were originally selected without having to scroll through the list

    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

  19. Show Workflow Activities As Dependency of Parent Workflow

    When selecting a Workflow Rule, its dependent components (i.e., email alerts) are not shown in the dependency view. They should be.

    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

  20. Improve comparison performance

    If there is one thing that is :-( about Gearset is that for moderate size orgs (a few thousand objects), the default 64 comparison takes too long.

    You want to initiate a deployment from source to target and, for whatever reason, you want to make sure you didn't miss anything that needs to be deployed

    So, to be safe, you initiate the 64 default comparison.

    And you wait (downloading, comparison). This can take several minutes. You go on to other tasks and your zeal to get the deployment done went off onto other things as the comparison time is too…

    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

  • Don't see your idea?

Feedback and Knowledge Base