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

223 results found

  1. Allow users to select custom fields even if the object does not exist in the target

    Would be great if GS allowed to select custom fields when doing a comparison even if the object does not exist in the target. If I am pushing changes to a repository I might want to only include the fields I created/modified and not the whole object.

    15 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Add the package Name to the page, when the package is Opened

    Currently when you Open a package like a draft deployment, the Name of the package does not appear. There is a message in top L-H 'Comparison finished' which is not very useful. Perhaps the package Name could go here. It will reduce confusion as you will be able to tell which package you have open. Thanks.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Show Metadata API version used to retrieve metadata for comparison on comparison result page

    It would save time and give confidence if the specific Metadata API version number used to retrieve the metadata was displayed on the comparison results page.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Precision Deployments (available for Layouts) for all the meta data

    Precision Deployments for Layout is a great improvement, it would be great to have the same feature for other meta data, particularely for : Fields picklists, global value sets, List Views, Reports, Profiles, Permission Sets and why not Lightning Pages, now that the Dynamic Form is available for Acc, Contacts & Opp

    19 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. exclude specific JSON keys when comparing Vlocity/Omnistudio metadata

    We are seeing Omniscripts showing as different on certain JSON keys. These keys always change and should be excluded from your comparison.
    The impact of this is Omniscript deployments require the LWCs to be compiled and if we deploy Omniscripts unintentionally, their LWCs are not recompiled and functionality breaks for the users.

    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. Deploy Now and Validate Package Buttons

    Presently, the Deploy Now and Validate Package buttons are positioned adjacent to each other. Occasionally, there is a risk of unintentionally selecting the Deploy Now button before the package has been validated. This can result in potential issues arising. To address this, I recommend the following actions:

    1. Enable the Deploy Now button only after the Validate Package process is successfully completed.
    2. Consider repositioning the buttons within the User Interface if both buttons share the same screen.
    3. Alternatively, place the Deploy Now button after the Validate Package screen in the sequence.

    Thanks.

    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. Deploy Managed Custom Filters Globally

    When we associate a custom filter with a particular CI job, and then make changes to the filter, give the user the option to push those changes to all jobs (list them out) that use that named filter.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Allow download of XML files from the comparisons page

    In some instances, we have to use the Metadata API to download XML files for analysis. However, the Metadata API is a pain to use. Even Salesforce recognizes this and suggests using a migration tool like Gearset to extract these: https://developer.salesforce.com/docs/atlas.en-us.246.0.api_meta.meta/api_meta/file_based.htm

    Since Gearset retrieves these files during comparison, it would be great if there was an option to download them to a zip file directly.

    Note: There is already a "Download Package" feature on the deployment page. However, we obviously can't add items to this page if there is no change between the orgs. So, if a similar feature were…

    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. distinguish between components of feature branch and what is syncing to main

    As a user of gearset deploying pull requests to multiple environments
    I want to be able to identify actual components of the feature branch vs. what is included for syncing to main/main branch for the org being deployed to
    So that there isn't the confusion of understanding what new/changes items are showing up in the commit information

    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. Cleanup Layout Assignments

    When you rename a Layout, the previous Layout Assignment won't be cleaned up on the Profile.
    This should be cleaned by the Repo dependency cleaner.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Please add Namespace/Package name as a column in the comparison view

    Currently , if I pull down metadata from managed packages (e.g. with the intention of committing the custom fields we've added to managed objects or committing the permissions we've updated) this means I get all the metadata in the comparison screen, with no way of filtering out the managed packages. An example of where this is a problem/cluttering the UI is Triggers/Classes - the contents of these is always hidden, so ideally i'd like to have a column to filter them out

    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. Integrate with Salesforce's Setup Audit Trail for Metadata Detection

    Many metadata types are referenced in Salesforce's Setup Audit Trail. An alternate way to detect changes to include could be querying Setup Audit Trail with a Start / End Date instead of asking user to select the necessary components.

    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. Remove Site.com from the Default Experience Cloud Comparison filter

    The Default Experience Cloud Comparison filter include the Site.com component. This component seems to cause problems with Experience Bundle deployments. I recommend this should be removed from the Default filter.

    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. Provide a list of Frequently Used Metadata Types for easy filtering

    I often don't know which metadata types I need to include in a comparison so I don't miss anything so I often use Compare All (takes forever!). I'd like to have Gearset suggest filters based on past deployments so I can confidently compare without having to wait a long 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Update the layout comparison view of Page layouts to reflect custom button/button changes on related lists. Currently XML view only

    The layout view does not show custom buttons added to related list/other button changes. This is visible in XML view, the layout view is slightly confusing as a result - The "Select all" tick at the top is present, but no other tick boxes, making it unclear what you are selecting unless you use XML view

    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. Date to date filter

    A date to date filter so as to ignore anything outside of that time window. Even if it could just be all the changes for one year, that would help.

    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. Save Filtered Metadata from a Comparison View as a New Custom Filter

    When running a compare, we'll often filter the list of metadata types in the results to eliminate types we're not interested in comparing. It would be nice to save the filtered view as a new Metadata Filter for use in a future compare.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Button for 'All the Differences' that gives all additions, deletions, and changes

    I'd love to have a button for 'all the things' (new, changed, and deleted). Currently, every time I run a compare, I use the All button and then turn off 'No Difference' on type.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Allow for Scheduled Comparisons

    Like Monitoring Jobs, allow users to choose a source, target, and metadata filter, and schedule when a comparison runs.

    The primary goal of this would be time savings. To have that data already retrieved and cached so you can go in, make your selections, and move toward deployment more quickly. Possible applications include recurring deployments, planning out your workday, etc. This addition would be for non-Integration users.

    6 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. quote term

    For CPQ Quote Term, the name column only shows "Approved" which is not meaningful.
    Please switch to using the "Name" field which is a auto generated number (e.g. QT-0209) that is displayed in the user interface and therefore a meaningful identifier.

    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