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. Add an option to ignore package version differences in Apex classes

    I see many differences between apex classes where the only difference is the package version(s), no difference in the code itself. It would be nice to have an option to filter these out so that only the apex classes are shown where the code is different.

    16 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 sort Custom Application XML

    While this can be done with VSC custom plugins for SFDX, I think it would be really beneficial if Gearset offered the ability to sort Custom App XML in comparisons in order to see what's actually changing between a source and target for lightning page activations. Due to the way SFDC generates this XML, the way page activations are ordered is very difficult to follow, and I think it's an opportunity to make that easier especially for declarative config users of Salesforce.

    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

  3. Identify that metadata is the same, even if ordered differently by metadata API

    There are a lot of instances where the comparison will identify metadata as different, but the only difference is the way the API is ordering the XML. I've seen it happen a lot with picklist values on multi-select picklist fields. It would be nice to be able to turn this on/off somehow so that metadata that isn't truly different won't show up in the difference compare.

    12 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. add the option to either hide source control locations where you do not have a connection, or allow a default SCM connection to be selected.

    We only use on source control service, so having to select 'Azure DevOps' before being able to select the repo/branch, is a small step that adds up over time.

    Being able to either hide services that you do not already have a connection for, or being able to default to a service, with the ability yo navigate back up and over, as needed. would be welcomed.

    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. Add an option to ignore location changes for Flow

    Hi, when reviewing changes for flows that are being deployed, it would be great to have a toggle option to hide or alternately color location changes which are just the location of elements on the flow canvas editor.
    <locationX>1353</locationX>
    <locationY>1305</locationY>

    Sometimes there are hundreds of location changes and it obscures the important information about what else changed.

    14 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

  6. Add the ability to run the problem analyzer while on the comparison screen

    I originally was going to request the ability to append the items found in problem analyzer to the list of selected components, when going back to view the comparison, but then I thought why not take it one step further, and move the problem analyzer feature to the comparison screen? Then, the items it finds/suggests, the user can add them to the package there, or choose to ignore them.

    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. Add an Undo Action/Functionality in the Comparison UI

    Add an Undo button to the comparison UI in case someone accidentally de-selects a component from the Selected Items tab. It would save time rather than having re-search for the component and lose your train of thought. You have this feature in Google Docs and sheets.

    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

  8. Ignore "trackHistory" comparison if an Org has "FALSE" and Git does not define this entry

    The Salesforce CLI system returns the Custom Field Metadata XML file without a "trackHistory" entry if it is set to false. This XML entry is optional in the Custom Field metadata type. However, once we deploy such metadata to the org and execute compare between a branch and the org again, it shows differences, saying that "trackHistory == false". But is "false" by default. So I would recommend you ignore this entry if SF Org returns FALSE and the VCS file does not have this item.

    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. Pop Out Diff File in Comparisons

    The current UI design for comparisons is very unfriendly to smaller screens. When working on a laptop viewing the comparison and the Diff files together is nearly impossible. It would be useful to be able to pop out a diff file or open it in another tab so it can be better viewed.

    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. Make org-org and org-VCS compare differences work the same

    There is no end to confusion on the part of the devops user when Gearset displays differences "differently" when comparison is org-org vs. org-VCS

    For example: https://docs.gearset.com/en/articles/3491009-are-profile-permissions-showing-up-as-new-or-deleted-when-you-know-it-s-not-the-case

    Gearset should apply a consistent principle - to see a Profile subcomponent, the compare filter should include both sides of the subcomponent (e.g. Profile + ApexClass to see ApexClassPermissions; Profile + Layout to see layoutAssignments; etc.)

    If both sides of the subcomponent are not included in the filter, then there's no difference to show.

    Note that these use cases must also be supported:

    Profile deleted in org; org->VCS compare should delete .profile file…

    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

  11. r.uzdavines@nextech.com

    It would be great if I could group my Selected Items into groups or Projects, so that I could filter and just see those. Now that I've added a bunch of items for different projects, it's a little hard to quickly decipher which project it applies to. I'd like to be able to double check each Project's list right before deploying to make sure I've added everything. Maybe you can add another column and allow the user to create new values for "Projects."

    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. Rename the Name bar in compare and deploy to : Name (api)

    Simple to implement, just a string rename...
    Rename the Name bar in compare and deploy to : Name (api)
    It would show clearly that the name displayed there is the API name, not the "label" name XD
    Cheerio

    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. sfdx repo deployment should be in subcomponents

    Context: Compare and Deploy from Org to a Repo.

    as i understand it, even if my repo is in SFDX format (Object subcomponents), Gearset still does the compare in the metadata format.
    it reads the components from sfdx, combines into a .object form, and then applies the changes to the .object file and then decomposes again.

    this is causing unintentional changes to be part of our PR

    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 →
  14. Enhance Metadata Filter Type Recognition

    Our team has struggled learning the Metadata API names of metadata types when compared to what items are called in change sets. One example would be to highlight Weblink when a user searches for Button.

    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 →
  15. Exclude list of Profiles from every compare

    With Pipelines / CI jobs, it is optimal if you can keep your VCS from getting cluttered with permissions for profiles you never use. Typically, these are standard SFDC profiles (SolutionManager, ContractManager, etc.)

    Rather than crafting a bunch of custom metadata filters that exclude these; it would be great to know that EVERY compare filter excluded an admin-defined list of Profiles

    The same principle could be applied to CustomObjects as there are a fleet of OOTB SFDC custom objects that most orgs never use and it would be great to see an admin-defined list of these excluded from every compare…

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

    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

  17. Items requiring the master-detail field be added - spurious Analyzer message

    If deploying from org->VCS and you get "Items requiring the master-detail field be added" - Gearset should look in the target and see if the various conditions (presence of master/detail fields/objects) already are present and avoid this analyzer message

    Once your VCS is fleshed out, it will have all the custom object/fields you need and then from that time forward, this analyzer message is irrelevant/annoying.

    Why should I see it every time I make any changes to the detail object for the rest of 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 →
  18. The ability to deploy only certain fields in a record type and not all fields

    If we want to promote a change to a single field in a record type, we're unable to because the file is pushed in it's entirety. We'd like the ability to view from list of available changes in a record type by field and select just the changes to the fields we want to promote.

    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 →
  19. Allow Package Cloning between Saved Comparison Pairs

    Please allow us to select a comparison pair as the source/destination when cloning a package. This will make it much easier to select the source and destination when cloning a package, and reduce the risks associated with accidentally selecting the wrong repo or branch or sandbox.

    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

  20. "Dismiss/Hide Item" option for any found comparison

    There are numerous "changes' that aren't actually changes (ex: logo images, Global Picklist set order). It'd be great to hide those those changes or dismiss them in a comparison to not look at them. Once it's dismissed, it's out of sight and there is no need to evaluate it every time you look at a saved comparison. It'd be clear that it was evaluated and not dismissed.

    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 →
← Previous 1 3 4 5 8 9
  • Don't see your idea?

Feedback and Knowledge Base