Help us improve Gearset

Welcome to the Gearset feedback forum. We love getting feedback from our users on how we can make Gearset even better.

Post your ideas and vote for others – let us know what’s important to you. We’re keen to hear about product improvements, new features, and bug fixes alike. We check this forum regularly and will keep ideas updated with their current status. If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Meta Data Searches

    Ability to do a meta data search like you can in eclipse or visual studio in gearset.

    For example search a custom field and where it is used within your org.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  3. Suppress irrelevant Suggested Fixes when deploying to git

    The problem analysis comes up with a number of Suggested Fixes which may make sense for improving Salesforce deployments, but which are unproductive when applied to git deployments.

    For example, the suggestion to remove TASK.WHAT_NAME, or to omit Standard Objects, will only serve to create a git repo which is an inaccurate reflection of the source org. Each time we deploy to that git repo, we will continue to have the same changes to select or omit, since the repo is missing objects and fields from the source org.

    When the deployment target is a git repo, all suggested fixes…

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?

    How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  5. Attach pdf items details in the email notif "Your organization has changed"

    When you receive a notification concerning a change into an organization you need to know quickly which items are changed.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add an option to share orgs by default

    Where we have a developer-manager, and a team of developers, it would be useful to be able to have a default for sharing org-connections where the manager always has access to their team's orgs.

    At the moment, we have to share each org one-by-one.

    This has caught us out where a dev team member validated a deployment, then went on holiday thinking that we could deploy it for them. They forgot to share the org-access, so we had to recreate the deployment to get it done.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add Support for Pre/Post Data Deployment Scripts

    Some of my more complex data objects require that I turn off Validation Rules during deployment, then back on again after deployment.

    Options that would work:

    * BEST: List of Validation rules under each object and and option to temporarily disable on a one-by-one basis during the deployment. A "Disable All Validation Rules During Deployment" option would be helpful if this feature is implemented.

    * BETTER: Ability to specify metadata xml to apply to each sobject pre and post deployment.

    * GOOD: Ability to specify anonymous Apex to execute pre and post deployment. This would involve a callout to the…

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Data  ·  Flag idea as inappropriate…  ·  Admin →
  8. Deploy data from local repository.

    It would be very helpful if we could deploy data from a local repository. We have different namespaces for internal packages and it would make data migration significantly easier if we could do it from a local machine where we'd switch the namespaces.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  10. Selectively filter managed package metadata without excluding unpackaged components

    Add the ability to filter in/out managed package elements from a comparison set at metadata type level. e.g. allow for the comparison of managed package objects and fields but exclude other managed package metadata types whilst allowing those types to be available for non-packaged constituents. More specifically for instance, exclude manage package page layouts and include managed package custom fields whilst including both unpackaged page layouts and custom fields in the comparison set.

    The reason for this is to minimise the comparison set which can reach limits due to size whilst including all mandatory metadata elements for a deploy.

    Using…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  11. When opening a draft/clone allow updating the content filter *before* the comparison

    When opening a draft deployment or cloning a deployment, please allow the option to update the content filter *before* running the comparison. As things are now, we have to wait for the comparison to finish before we can change the filter, and then we have to wait for the comparison to run again.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  13. 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

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  15. Summary pages should always include ALL changed files

    I believe this to be a bug, but it might be intentional. In any case, the current functionality is, in my opinion, poorly conceived.

    If a user adds a deletion to a comparison between an org and git, the deleted metadata is the only item that will show up in Gearset. However, if you inspect the resulting commit in git, you will see that the metadata was deleted along with all of the profiles, layouts, etc that had to be changed as a side effect.

    I'm completely fine with Gearset detecting these dependencies and making the changes to them. It…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow individual lines to be selected for inclusion or exclusion of a deployment

    Allow individual lines to be selected for inclusion or exclusion of a deployment

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  17. Mass delete option for deployment history

    You can select multiple deployment history rows to "combine packages", but it'd be nice to be able to "delete all selected".

    This is useful if you'd like to clean up a cluttered history to only see successes and what actually went in to an org.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  18. enumerate unsupported metadata in Manage Custom Filters

    In Manage Custom Filters dialog, Gearset should link to

    a) https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_unsupported_types.htm
    b) a Gearset list of Metadata API-supported but not yet GS-supported metadata types

    saves devops person wondering why certain metadata can't be deployed

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  19. There should be an option to schedule unit test jobs weekly in Gearset

    Hi Gearset,
    I would suggest you to provide an extra option where we can select weekly ,daily or monthly schedule jobs in Unit Testing Jobs.

    Thank you,

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  20. Link to test runs in Slack messages (or Slack messsage customisaton/templating)

    I have automated test jobs post about failed tests to our Slack. I want the posted Slack message to include a direct (though maybe shortened) link to the "Test run details" so that when we see Gearset telling us about some tests starting to fail I would be one click away from seeing a view of failed tests the message is talking about.

    Next/bigger step would be a way to shape the Slack messages ourselves. The most basic templating setup where I could write my own Slack message with some placeholders like {{instance_name}} or {{failed_tests_link}}..

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  • Don't see your idea?

Feedback and Knowledge Base