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

246 results found

  1. Filter (regex) on Outbound Message names within Workflows in Metadata Comparison

    Our sandboxes all point to different URLs within the Outbound Message action.

    We want to include workflows in our CI job that backfills production changes into test environments.

    However, we cannot do this as there's no way to exclude outbound messages in the filter.

    In the "Metadata Comparison Filter", you only have the option to add regex or select specific items at the object level within "Workflow".

    If you apply a regex to hit the outbound message name, it doesn't actually hit that outbound message name and only searches within the object name.

    You can only use regex when you're…

    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. 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. push new profile FLS entries into the profile file in alphabetical order

    When picking up new FLS entries, by default these are added at the bottom of the list of FLS.

    This causes issues when also having save jobs picking up changes, as this can result in duplicate FLS being added to a branch.

    Please update code structuring, so new FLS is added in the correct place in the MD files.

    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. Don't allow duplicate fields in comparison.

    If I have a field with name example category. Somehow the same field has been added to the object xml file it needs to throw an error at the time of comparison.

    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. 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. (this would be something like grep -e 'this' -e 'that')

    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…

    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. Allow filtering by Deployment Stage/Metadata Subset during comparison

    This Gearset article describes some very logical phases for performing a large deployment:
    https://docs.gearset.com/metadata-deployment-guides/splitting-a-complex-deployment-into-stages

    It would be nice if there were built-in comparisons to show each subset of metadata.

    For example if you were on phase 1 of the deployment you could filter your comparison to just "Data Tier" and Gearset would pre-filter the relevant metadata.

    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. When viewing comparisons, allow the "Export All..." to utilize existing filters

    When viewing a comparison... I have various filters set to exclude certain differences like "Reports, "Permission Sets". It would be nice if you provided an option on the "Export All..." page to either export everything (disregard filters) like it does now, or to respect any filters that currently exist on the comparison so that I only see the values shown on the page based on my 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)
  8. Suggest related metadata for selected types in filter

    Gearset provides some very useful documentation on the importance of including groups of related metadata in a filter.

    https://docs.gearset.com/metadata-deployment-guides/using-gearset-to-deploy-profiles

    It would be very helpful if the Manage Filters dialog implemented these suggestions. For example, when a Profile is included in the filter, the user should be prompted to also select Profile Password Policy, Profile Session Setting, External Data Source, Apex pages, Layouts, and Custom Objects. Otherwise, the likelihood of Gearset assembling an accurate Profile without all of the related components will be slim.

    Gearset obviously has deep knowledge of metadata semantics and dependencies. The Manage Filter page needs to reflect…

    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. Show *all* matching items on All Items, even if they haven't been changed.

    I couldn't find a field that I was looking for today, despite searching for it specifically, because it was hidden inside it's parent object. I understand that the reason for this was something to do with there being no difference on the field (and I appreciate that the reason is to avoid clogging up the screen!), but if you're searching for a specific field, I think it should really show up...

    Took me bothering someone on live chat to figure out what was going on.

    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. Selection Count Mismatch

    The Selection count on ‘Compare and Deploy’ page doesn’t match with ‘Items Selected’ on ‘Draft Deployment’ when a draft deployment is opened. Having this in sync will help user that all selections are going in the deployment.

    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. Be able to exclude single items from comparison

    E.g. If I generally want to include all Custom fields for all Objects in the comparison, but there’s one specific field that I don’t ever want to send across to the target org, it’ll keep popping up and I’ll have to uncheck it each 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)
  12. Track Items Added to Draft Packages

    It would be nice to be able to see which items within a comparison are part of Draft Packages. We have a need to build multiple packages from a single Comparison of Instances. This can be done by creating many Drafts, but it is sometimes difficult to know if items have been added to a draft package already. If we could visually see this, it would allow us to generate and confirm our packages much faster.

    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. Show the Label as a column in the comparison screen

    At present the comparison screen, Name column, only shows the information from the API name, but not the Label (as seen in Setup > Object Manager > Label column).

    When the Label is wildly different from the API name, is would be super useful to have the Label displayed as a column, instead of having to find it in the XML viewer.

    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 the ability to "uncheck" No DIfference items on the Selected Items tab

    When cloning previous deployments, there are may cases where items may have been previously deployed, so the now would show as "No Difference". Currently these items can not be unselected for the deployment. It would be useful to be able to remove these from a current deployment to keep the deployment clean.

    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. Allow XML package for org snapshot/daily monitoring

    Allow XML package for org snapshot/daily monitoring. This is to take the previous day's design to be downloaded in xml format that we can open in eclipse IDE.

    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. Show rows that have no set "Changed On" date when applying a date filter.

    Currently the moment you deselect a single specific date, all blank dates are also filtered out.

    I would expect only the items with the given date be removed from the list.

    This has become apparent now that the sort order of dates in the pulldown bug has been fixed.

    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. show which deployment each metadata was a part of when doing a bulk clone.

    When doing a bulk clone, each metadata should show what previous deployment it was a part of as to allow us to verify that the bulk clone worked. Another use case is that it would allow us to find a deployment we know has changed and be able to remove or change the metadata quickly.

    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. Cache deployment inspection results

    It would be great if deployment inspection results were cached, such that the results for an identical set of metadata are available without spending the time to recheck everything.

    Use case: A comparison is performed and all changes selected. Deployment inspection is performed and recommendations are made for items to add/exclude. I select a subset of recommendations, and move forward with validation. The validation fails. The same comparison is reopened and again all metadata is selected (with the intention of selecting more of the add/export recommendations resulting from the inspection). At this point, the inspection is rerun, even though 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. Add an option to use a custom "Gearset format" for the source control output

    The XML that comes from Salesforce is weirdly bundled together. When changes are made it's really hard to reconcile two branches in source control when merging.

    When comparing, Gearset nicely decomposes changes into smaller chunks. So instead of putting that back into the usual XML, an option to store that "internal format" and even just stick it as JSON or similar.

    After all - it'll be Gearset reading it back in to compare to an org next time, and smaller changes will be easier to merge as they won't conflict inside horrendously large XML files

    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. refresh comparison UX - echo the filter used in the original comparison

    When you click Refresh Comparison, the dialog does not echo anywhere the original filter name used in the comparison-being-refreshed. You just get a x/y filters being used.

    Always good to remind the user as to which filters were originally selected without having to scroll through 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)
  • Don't see your idea?

Feedback and Knowledge Base