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

227 results found

  1. Namespace Mapping for Managed Packages

    We are an ISV partner with a managed package we sell to lots of customers. That means our package is namespaced. However with a distributed development team and multiple dev orgs, all source code is not namespaced, and is maintained in source control (github) without namespaces. Only upon unit test and promotion to the package org, does the namespace get added. This results in two basic problems (and others). 1) comparisons between unit test and package result in almost everything being flagged as "changed" due to the namespace, and 2) all aura components are always flagged as "new" when they…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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. Distinguish between code changes and just API metadata changes for Apex in Comparison Window

    For large code comparisons, it'd be great to have the ability to see when it's just a change in API vs. actual differences. Right now, you'd have to click on every row to see what the actual change was.

    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. Add a column to indicate if XML matches if order doesn't matter

    See this link: https://docs.gearset.com/en/articles/2413367-why-is-xml-order-of-some-metadata-in-the-comparison-results-different

    Sometimes, the XML of an item in sandbox/production can be the same, but not in the same order. This leads to false positives showing up in the list as "changed items".

    I understand that sometimes order matters (eg: in picklists) but maybe there could be an additional column which shows if there are no differences if you ignore order? Maybe even a setting to turn the column on and off so it's not confusing?

    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. Ability to tell what metadata filter someone used in a compare/deployment

    For compliance, troubleshooting, and collaboration purposes it would be great to see what metadata filter a user used on their comparison

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Ignore sfdx-project.json file in order to compare code using Metadata API structure

    I need use the sfdx-project.json file in order to integrate with VS
    code, but using Metadata API structure.
    Apparently, Gearset is looking for this file to define if is a metadata API or SFDX structure,

    So I need a ignore looking for this file, in order to compare as metadata API structure.

    Thank you.

    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. Compare metadata by "Changed Date" for both "Source" and "Target"

    In "Compare and Deploy", is there a way to add a column for "Changed Date" for the Source item, in addition to the Target item?

    I want to select all the items which were more recently changed in the Source than in the Target. In my current large org compare-and-deploy, I see many items which are different but the one in the Target was more recently changed, so I don't want to overwrite that item in the Target.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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)
  9. Only display active branches when displaying branches from a bit bucket cloud repository

    Only display active branches when displaying branches from a bit bucket cloud repository

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Mark items as already reviewed earlier

    Today we are gearing up for a major deploy so we are deploying many different changes into gitHub. It would be nice to be able to mark whole sections of content as already reviewed such that any new comparison could ignore all of that content. Then we could look at only the new or newly changed/deleted content.

    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)
  11. Allow for selecting/unselecting Filter by Package.xml

    When doing a clone or a refresh comparison today the ability does not exist to add or remove the option of whether you are filtering by package.xml. I would like to see this added.

    For us what might occur at times is that we have a release occur where this is accidentally selected and we find that a number of items are missing and due to this being selected. We have no way to remove the selection and have ended up starting over. One of a number of scenarios where it would be nice to have the option to do…

    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)
  12. Ability to see count of items per metadata type

    Ability to see count of items per metadata type at the Comparison Result 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)
  13. Warn the user of unsaved changes to an org compare filter

    It would be nice if we got a warning if we have selected specific components in a filter but havent saved the filter when we hit OK. I've lost a lot of work on a custom filter because I forgot to hit 'Save' - I would have thought it would auto-save when you hit OK.

    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)
  14. The comparison screen takes too long to load and times out with large packages.

    With large packages the comparison screen takes too long to load, >15 min, and can cause Chrome browser to time out. Can we have an option to not load the details of the differences in the bottom panel, only object names and then click a button to download only difference for a particular item on-demand? I normally don't need to see the diff

    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. Make it easier to select all custom field translations for deployment

    Right now if you want to select translations for certain custom fields, it is necessary to expand the sub-components for each field and select the translation. The second option is to go to the custom object and expand the sub-components in order to check translations which will include all the custom field translations for this object.
    It would be helpful to get a way to select the translations for specific custom fields in the deployment.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Allow deployments across managed package versions

    Gearset does not allow comparisons or deployments of custom metadata on managed packages if the versions are different. We got ourselves in a situation where a package in the sandbox was a higher beta version that we couldn't upgrade to. This required us to do all the field deployments via changsets.

    Adding a warning for deployments across managed package versions would be ideal as most changes one would deploy wouldn't necessarily cause any issues.

    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)
  17. Create a way to apply a regex to all currently selected metadata types when building a filter

    The regex support you currently have doesn't really allow for complex (multi-match) regex matching, which is probably ok

    If I select, say 116 of the 124 metadata types identified, and then have to apply a regex pattern to each one, it gets pretty tedious. Click-paste-apply 116 times, and then 116 again for the other half of the complex match. I'd write a tool to automate configuring a filter in gearset. :)

    If I "select all" then deselect the 8 types i don't want, and THEN apply a regex to all types, that would be pretty great.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Segregate metadata changes due to SFDC release

    If I compare my production org to a preview sandbox that has been upgraded to the new release, I see some changed, new, and deleted items that appear to be due to the upgrade. For the most part it probably doesn't make sense (or isn't possible) to deploy those differences in either direction, so it would be nice to be able to exclude them or have them flagged somehow.

    For example, in Winter '20 several fields were added to the OpportunityContactRole object. They show up as custom fields in the comparison. If I try to deploy them to production, the…

    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. Show summary of selected Filter conditions

    Would like ability to select a saved filter and see a summary of all the 'checked' filter conditions in it. Useful in verifying a filter or shared filter before using it.

    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. Export of the Comparison Results

    My Suggestion: For our Customer i need to create a Documentation with all the Metadata Information from the Comparison. Even for Things which are not different.
    A CSV Table would be great and a HTML Documentation would be awsome :)

    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

    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