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

1260 results found

  1. Display "No Difference" metadata sources on Deployment Summary page

    On the "Deployment Summary Page" it would be great to add a column to the list of metadata components added which shows for the "No Difference" items showing the source piece(s) of metadata which is causing this "No Difference" to be included.

    This would dramatically help in the narrowing down of why a piece of metadata is included - especially if that piece of "No Difference" is a managed package and cannot be altered. In a large deployment, trying to identify a root cause for why a component was added is quite difficult. Simply giving a way to track back…

    1 vote
    How important is this to you?
  2. Categorize Meta Data Filters

    Allow the custom meta data filters to be categorize or put in folders. You could organize your filters by customer, deployment type, etc..

    4 votes
    How important is this to you?
  3. Email2Case Deployment for Selected Email2Case Setting

    When deploying email2Case i am unable to choose particular email2Case that i need to deploy and end up choose all the email to case settings. Needed feature to deploy this selectively.

    1 vote
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?
  4. Provide more detail in Monitoring notifications

    Right now, the Monitoring job notifications (Slack especially) provide very little detail as to what actually changed.

    Ideally, I'd be able to see right in the message (or in a threaded reply), the first X number of metadata changes made. If there are more than that, then providing a direct link to the detail page in Gearset would be great.

    As of now, it simply just says "there were changes", with no detail or way to easily see the changes in Gearset...which is not terribly useful.

    4 votes
    How important is this to you?
  5. Use triggering branch as source branch in git-sourced CI jobs

    Currently:
    We have to define a single fixed source branch in a CI job, when it has a Git-Source.

    Desired:
    Option to say "use triggering branch". It should use the branch, where current commit-hook-call comes from.

    It should allow Pipelines to test also all development branches e.g. with "Validation only" CI-job.

    11 votes
    How important is this to you?
  6. Plain text list export of metadata

    There are times when I'm in an email thread with other developers and I want to share a list of metadata that I'm trying to deploy via Gearset. It would be nice to have a button after a validation or deployment (failure or success) that copies in plain text a list of everything in the deployment. The list not only has the name of each metadata, but also the type of metadata it is.

    1 vote
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?
  7. Allow Data Deployment to filter lookup fields on fetched data

    Currently, when doing a data deployment Gearset will let you know of all the referenced objects from the object you selected. What it doesn't do is the opposite of that - let you know all the objects that reference your object with a lookup.

    It'd be great if we could add a filter to utilize some data pulled in a fetch/query during data deployment.

    ex. field (TeamMember.ProjectLookup_c in {returned Project results in query in previous step of data deployment).

    6 votes
    How important is this to you?
  8. Improve error handling for invalid XML metadata files

    Currently, when there is an error with an XML metadata file (usually introduced by git merges), Gearset will produce an error, either in the Initializing Comparison, or Checking Deployment stages, stating simply that "An unknown error occurred."

    If Gearset instead ran the XML from source control through an XML validator using the Partner WSDL XMLSchema, then we could get file-level validation errors if the XML doesn't conform to what Salesforce's Metadata API will accept.

    e.g.:
    $ xmlstarlet val -e -s ~/Downloads/salesforce-schema.xml force-app/main/default/profiles/Marketing.profile-meta.xml
    force-app/main/default/profiles/Marketing.profile-meta.xml:17108.15: Element '{http://soap.sforce.com/2006/04/metadata}field': This element is not expected.
    force-app/main/default/profiles/Marketing.profile-meta.xml - invalid

    1 vote
    How important is this to you?
  9. Reporting

    have a way to dump a csv of the description of objects. i need to find a way to see what fields are encrypted.

    1 vote
    1 comment  ·  New feature  ·  Admin →
    How important is this to you?
  10. 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
    How important is this to you?
  11. Add the option to note successfully deployed components in CI notifications

    When a CI job is configured to post to slack, and a job fails, it is very useful to see the message posted with information about what failed (error message, number of components that failed).

    However, when a CI job succeeds, it only shows the counts of changed/new/deleted objects.

    It would be very useful to have the option to list out what was deployed - this would make it easier for devs/qa users who monitor these slack notifications to understand which deployments are relevant to them at a glance.

    2 votes
    How important is this to you?
  12. Pulling object dependencies during data backup

    A cool feature would be the ability for Data backup to have the ability to select object dependencies when you select a particular object for instances where you want to backup a subset of data and not just your entire org

    2 votes
    0 comments  ·  Data backup  ·  Admin →
    How important is this to you?
  13. Better error reporting when CI jobs fail.

    Better error reporting when CI jobs fail. Many times I open a failed job and there are no errors reported.

    7 votes
    How important is this to you?
  14. Save deployment analysis suggestions and list of test classes

    In order to make deployments more repeatable between orgs please allow a way to save the selection of deployment analysis suggestions an d list of test classes with a package. With a large package it can be difficult having to document or remember the same selections used in deployment to UAT org for Production deployment.

    5 votes
    How important is this to you?
  15. On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen.

    On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen. We need a quick way to make sure that item level filtering is being used on each metadata type

    1 vote
    How important is this to you?
  16. 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
    How important is this to you?
  17. Set fields to a specific value during a data deployment

    When deploying Data, it would be nice to be able to set field values. It could be just to null them or set a value. It could be part of the configuration or data masking.

    13 votes
    How important is this to you?
  18. track metadata filter changes

    Filters are shared by default. However, if someone changes the filter, I cannot tell what has been changed, who made the change or when it was changed. Ideally, I'd like a version history for each filter.

    6 votes
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?
  19. 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
    How important is this to you?
  20. Permission sets not deploying correctly

    When deploying a permission set, it was being deployed without the permissions checked, even though Gearset detects that the permission is checked in the metadata compare.

    4 votes
    1 comment  ·  Bug  ·  Admin →
    How important is this to you?
  • Don't see your idea?

Feedback and Knowledge Base