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

    7 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. Refresh specific item in comparison through context menu

    It would be great to refresh a specific item within a comparison that I know has changed since the last comparison.

    68 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. Option to ignore: <personAccountDefault> in XML

    When comparing XML for RecordType permissions in Profiles, some Sandboxes return:
    <personAccountDefault>true</personAccountDefault>

    As part of the XML, even though person accounts are not enabled, this makes comparing annoying.

    It would be nice to have an option to ignore this.

    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 →
  4. Add support for deploying a name change to a SFDC component (such as profile)

    We occasionally change profile names during permssions clean-up projects. Currently, when you deploy a profile with a changed name, Gearset recognizes it as a "new" and a "deleted" profile, instead of a single "changed" component, which makes the deployment challenging.

    I know that the name is used as an identifier, since the Id may not always match between source and target. However, if you add support for this, the tool could try to identify components with name changes by looking for the same Id in source and target with a changed name.

    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

  5. Allow exporting of custom filter settings

    I have some regexes configured specifically for continuous integration, changing these would likely break our CI process. I would like to be able to export a JSON or YAML (or whatever sensible text based format) of my filter configuration, so I can easily view which metadata I'm selecting and excluding through regex, and possibly commit this file to source control.

    This is primarily because our team shares filters, and I'd hate to lose the configuration because of someone mucking up.

    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. Ability to cherry pick changes in a file

    When comparing changes between a source org and a target org for a given file/metadata component, it will be great to have the ability to choose which change(s) should be promoted from the source org to the target org.

    Presently, it's an all-or-nothing scenario i.e. either one deploys all the changes to a given file from source to target or deploys none. As a workaround, we cherry pick changes to a file using VSCode and then deploy to the target org using VSCode –– which is the exception to our "all metadata changes must be deployed through Gearset" policy.

    Adding…

    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

  7. Allow refresh comparison only for selected items, instead of refreshing the entire metadata filter

    When selecting a metadata filter and then running a comparison and reviewing the results, sometimes you find that a small change is needed to one metadata item. You make the change in the source org, but now the comparison needs to be refreshed.

    Instead of having to refresh the entire comparison, it would be great and save a lot of time to be able to select and refresh specific metadata items from the comparison page.

    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 →
  8. Display Permission Set changes as one entry

    When working with Permission Set changes, it sometimes would be useful to see them grouped by Permission Set instead of being disaggregated by field. For example, we are migrating from using Profiles to Permission sets to grant all access. Currently, if we make changes to many (>100) fields in two different Permission Sets, we have to review many (>100) entries. Also, grouping by permission set would allow us to deploy changes to one Permission Set while ignoring the other.

    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 →
  9. Last Modified in Metadata Filter

    It would be great if I could set a "last modified" filter when setting which metadata to pull. Rather than go to Apex Classes, wait for the list to refresh, then cherry-pick them, it would be great to simply compare Apex classes modified today, or in the last 30 days, or in the last hour, etc.

    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 →
  10. Individual Assignment ruleEntry

    Please Allow us to Deploy individual Assignment ruleEntry rather than the whole file/set, similar to components in other objects, sharing rules.

    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 →
  11. 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 →
  12. Ability to choose whether or not to respect the forceignore file

    Would like a checkbox on the comparison screen that allows me to choose whether or not the comparison will respect the contents of the forceignore file. (Similar to the checkbox allowing you to choose whether or not the comparison should use the package.xml file).

    Our usage of Gearset does not align with our usage of the forceignore file for automated deployments. In fact, we often use Gearset to manually compare and/or deploy items that we specifically ignore for automated deployments.

    Summary of problem this new feature has introduced:
    We use gearset for org -> git deployments, and for git ->…

    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 →
  13. The Action Order in the XML should follow the sortOrder

    Sometimes there is a difference between a object because the order of the platformActionListItems are different. Sometimes an item with order 0 comes first, but it is possible that an item with 9 comes first. This is probably an error in Salesforce API, but Gearset should order this list before the comparison so 0 will always be the first item.

    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

  14. Avoid spurious differences in LeadConvert

    SFDC seems to retrieve the lead convert settings in non-deterministic order between orgs . Display only true changes/adds/deletes rather than differences in ordering of the mappings as they make no difference to the runtime execution of Lead Conversion

    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

  15. Add "Manage Custom Filters" button next to Metadata Comparison Filter dropdown

    I find myself always going into the "Manage custom filters" screen as it allows you to see what metadata you're including and even change the selected filter.

    To get to that screen always requires a click on the drop down (Metadata Comparison Filter) and then another click at the very top on "Manage Custom Filters".

    It'd be great if the "Manage Custom filters" gear/button was displayed on the main UI next to the "Metadata Comparison Filter" to save time (avoid clicking on the dropdown) and allow users to quickly get to the Manage Custom filters screen which contains all you…

    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

  16. Use package xml to populate metadata filter

    I suggest to add the ability to upload the package.xml manifest files to populate the metadata filter before the comparison step of an org to git or org to org deployment.

    A lot of Salesforce developers use package.xml files locally to deploy some parts of the functionality in order to speed up the deployment process.
    Currently, Gearset allows you to select the components via Custom Filters, but it is slow to select about 20 components manually. Uploading the package manifest from the local machine can speed up the process very much,

    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

  17. Consistently position the Source > Target UI element

    In the various screens of a comparison + deployment, the Source > Target element jumps around:
    - Top of the page for the Comparing... page
    - Middle of the page for the Compare page
    - Top-left for the Comparison Summary page
    - Top-right for the Deployment page
    - Middle of the page for the Deployment Results page

    During this process, I am constantly double-checking to make sure that I am using the correct Source & Destination environments so as not to make a mistake. Instead of scanning the entire screen to see where this is annotated, I would like to…

    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

  18. Display more workflow subcomponents under Workflow for Metadata filter

    Currently, two sub-components display under Workflow when selecting metadata types within a filter.


    1. WorkflowAlert

    2. WorkflowRule

    There's more sub-components than those two and I'd argue that there's two that are frequently used that should be included for visibility


    1. WorkflowFieldUpdate

    2. WorkflowOutboundMessage

    There's 2 more, but these may be used less frequently and not needed for visibility


    1. WorkflowKnowledgePublish

    2. WorkflowTask

    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. csv export comparison CSV doesn't identify source and targets

    When you export a comparison (e.g. selected items), the CSV has column headers for Source and Target. So, someone looking at the CSV can't tell what the source was (org friendly name/repo+branch name) or what the target was (" ")

    The file name identifies the source org by xxx@example.com .... but no friendly name which is key when source is a scratch org. No identification of the target at all in the csv file name.

    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 →
  20. Add support for the WorkSkillRouting metadata type

    WorkSkillRouting is a key object in the configuration of Skills-based Routing for omni-channel (using Attribute Setup, not apex class), please add support for this object to enable comparison and deployment.

    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

← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Feedback and Knowledge Base