Skip to content

Help us improve Gearset

We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.

If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

247 results found

  1. Multiple screens

    I work with 2-3 screens. It would be great to be able to split the comparison settings to one screen and have the xml, flow navigator, lightning page visualizer,... on another screen. That way users can see more as they work. As a photographer I use Adobe photoshop and lightroom both applications allow splitting the controls and output.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Allow Adjusted Column Sizes to Persist in the Comparison Table

    Have adjusted column sizes persist once they've been adjusted in the comparison table instead of resetting with each selection. Deploying changes to permission sets could be dramatically streamlined if it's possible to maintain resized columns. If column sizes were set to accommodate the name instead of giving them all the same size, that would also be a huge improvement. The other columns don't include as much info as the name column so it's a waste to give them so much space. It is also inconvenient to caret down in permission sets especially when looking for multiple fields in one permission…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Cancel Comparison

    I would like to be able to cancel comparison jobs so that I can totally reset the metadata selections and run it at a different time instead of making the modifications during its run time and possibly taking longer because of the changes.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Auto navigate to next conflict after resolve

    After I have resolved a file/metadata component I would like it to auto navigate to the next item in the list.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Custom Sort Conflict files by metadata type

    I would like to be able to sort conflicting files by metadata type in the conflict screen. That way I can resolve conflicts in a more organized fashion.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add support to deploy Digital Experiences (LWR) using Digital Experience Bundle Components

    Similiarly to how you can deploy metadata for non-LWR Digital Experiences (Aura templates), where you can select different metadata changes individually using Experience Bundle Components, rather than deploying all your changes at once, it would be great if that option is available for Digital Experiences running on LWR (Digital Experience Bundle)

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Save sort order in Saved comparison pairs

    It would be nice that the chosen sort order of the saved comparison pairs could be saved.
    If I choose to sort the saved comparison pairs on Friendly name and i open a new tab of gearset, the saved comparison pairs in the new tab are sorted on last used. It would be nice that in the new tab, the saved comparison pairs are sorted based on the same column as the previous tab.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Add an option to ignore API version differences during comparisons

    When comparing Apex, and other files with API versions the difference engine will mark any files with higher API version as "changed", even if the API version is the only change. This can be undesirable when there have been bulk updates to the API version that have not been made in the development environments. It would be great if the comparison engine could make it clearer when the only difference between two files is an API version (especially when the target is on a higher API version)

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Picklist Comparison should show if value is active/inactive

    When comparing a picklist in which we have deactivated values, the simplified comparison visualization shows the deactivated values as being "added" (in green, on the source side).

    The XML reveals <isactive>false</isactive> is being added, but the simplified view seems to suggest new values are added instead

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Use location of metadata in source branch or local folder when adding to target branch

    When adding a file from a branch or local folder (source) to another branch (target) not having the file, use its location in the source as the location in the target.

    Currently all new files are placed in the default folder [1].

    Let's assume a new file, "HelloWorld.cls", in the source is located in .../force-app/main/default/classes/special/ and that class doesn't exist in the target. When the deployment is complete the file should exist in the target's .../force-app/main/default/classes/special/ folder, matching its location in the source. Currently it would be placed in .../force-app/main/default/classes/.

    [1] https://docs.gearset.com/en/articles/2835001-structuring-your-source-control-repository

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Add support for CMS Collections

    Please add support for CMS Collections in the comparison filters as well as the deployments and CI jobs.
    We're working with CMS Collections in our current developments of a customer community and we'd like to deploy this metadata as well.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Vlocity Metadata Types collapse during Compare & Deploy

    When you start the Compare & Deploy, for Salesforce Objects, you see all the metadata types broken out as they get completed for 204 types. For Vlocity there are 83 types to select, but when you run the comparison, it collapses to just 1 type of Vlocity. It should show progress similar to hwo the Salesforce Metadata types work

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Filter metadata types based on whether org is licensed for that metadata or user permissions for that metadata

    Compare 2.0 Metadata types

    Why am I seeing Fuel Type and Fuel Type Sustainability Unit of Measure ? Running user needs a special permission set to see these metadata types and I, as running user in Gearset, don’t have this permission set.

    This is an example of a general suggestion wherein if the source org/running user isn’t licensed/permissioned for some SFDC metadata, it shouldn’t appear in the (lengthy) enumeration of metadata types

    Other examples are Live Chat XXX, PaymentGatewayProvider, SchedulingXXX,SustainabilityUom,SustnUomConversion, WebStoreXXX and many more

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Allow XML comparison to be exported

    Being able to extract the XML for the change and the target's differences would allow us to analyze and track label/code changes versus just ordering or location changes.

    My issue is similar to the "Enhance XML meta data comparison to ignore changes in XML order" and "Export Comparison details all items" and "Allow download of XML files from the comparisons 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Search with components returned by metadata comparison

    Performing a search across the returned components xml would be helpful. In our org we add a JIRA ticket reference to the Description - having the ability to search for the ticket number string would help narrow the list.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Ability to move existing field to be under another section on layout

    If I have multiple sections on my layout.
    I have a specific field under one layout section, but now I changed the layout so the field no is moved to another section.
    Now I can't do that because the compare and deploy forces me to override the existing section where the field is under.
    My intention is to move the field place to be under another section and not delete the other layout section

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Add exclusion filters for Pipelines

    Currently, the metadata filters in pipeline (CI) jobs are either all of a type of metadata, or a defined subset. There is no option to include all, except for a couple of objects, which is oftentimes required.
    Please consider adding a negative (exclusion) filter for CI jobs, in addition to the existing positive (inclusion) filters.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Include DataWeaveResource in comparisons and deployments

    DataWeaveResource has been around for a few releases and is deployable via the Metadata API, but is not supported by Gearset yet. Please include 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Persist Selection to Include/Exclude Managed Packages in Compare 2.0

    When using the new compare, the default is to exclude managed packages. However, we'd like to always include them, so it would be nice to persist the selection from one compare to the next.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base