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

1357 results found

  1. Explicitly set object-level permissions, even if these are omitted from XML provided by Salesforce API

    Valerio recommended that I post this suggestion following a discussion on 29 August 2019.

    Issue reference:
    https://docs.gearset.com/en/articles/3226459-a-note-on-deploying-custom-object-permissions-on-new-profiles

    Issue:
    1. Remove all object-level access for "Lead" from a custom profile in a source org
    2. Deploy this profile to a target org
    3. The profile in the target org will have access to the "Lead" object ENABLED, because this access is included in the Standard User profile (see document link above)

    The workaround (deploying and then deploying again) is cumbersome and not always practical, e.g. if making automated, one-step deployments outside of Gearset. Failing to make a second deployment means that…

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

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

    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)
  4. 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)
  5. 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

    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. 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)
  7. 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)
  8. Remove the "run as specific user" completely from the dashboard prior to deployment (set the options to "Run as

    Add during problem analysis:

    Remove the "run as specific user" completely from the dashboard prior to deployment (set the options to "Run as logged-in user"). Deploy, then change it back to whatever you need. Based on https://developer.salesforce.com/forums/?id=906F0000000DCJPIA4

    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)
  9. 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

    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

    0 comments  ·  Bug  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    47 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. Deploy SOAP APIs like Permissionset assignment

    I am able to deploy profile components and permission sets separately. But the permission set assignment is part of salesforce SOAP API and I couldn't deploy the same using GearSet.
    Kindly provide deployment options not only for Metadata API, also SOAP APIs

    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)
  12. Provide ordering for metadata elements when committing to version control

    When metadata is retrieved from Salesforce the order of child nodes is not guaranteed and results in false-positive changes when committing to version control. Usually this will be something simple like workflow actions/criteria appearing out-of-order which can be compared manually. However, recently we've noticed entire profiles being committed with every permissions element out-of-order, resulting in a change set with ~20k lines where the actual change is impossible to visualize.

    Gearset should provide a feature to 'order' child XML elements alphabetically by name in order to provide consistent commits to version control and eliminate false-positives.

    10 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)
  13. 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. Allow reauthorization of git/Bitbucket tokens used by CI jobs

    Currently, if the OAuth tokens used for a Bitbucket integration are refreshed, any existing CI job will not adopt the newly authorized token. In fact, there is no way to even edit the job to use the new credentials; the job must be completely deleted and created anew.

    However, in the case of Salesforce OAuth tokens, Gearset already has a Reauthorize button, along with facilities for re-associating the new credentials with saved orgs and saved CI jobs. Please enable similar reauthorization mecahnics and credential saving for other Oauth integrations, especially Bitbucket Server, so that CI jobs will not need to…

    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)
  15. Inline Editing of metadata

    Inline Editing of metadata
    In order to make our deployment successful we had to download the package, modify the version numbers on the flow definitions, and then compare the local package to the target org. It would be very helpful if we can edit the metadata XML in the UI so we can fix the version numbers.

    108 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)

    Hello. A large number of commenters requested the ability to carry out value replacements as part of metadata deployments. 

    Gearset now offers a feature called Environment Variables that lets you do just that!

    It works with both manual and CI deployments and lets you target either a Salesforce org or a Git repo of your choice. And, for a number of key metadata types, you can even specify the exact 'field' where the replacement should take place.

    If you have any feedback on the Environment Variables feature, please open a new feature request or simply let us know in the in-app chat. 

    Thank you for upvoting this feature request and we hope that you will find the Environment Variables feature useful.

    Blog post:  https://gearset.com/blog/environment-variables/

    Support doc:  https://docs.gearset.com/en/articles/5557015-using-environment-variables-in-gearset  

  16. Allow the use of cached metadata during comparisons

    Over the past 2 days we ran multiple comparisons between salesforce orgs. Nothing was changed in the target org but some fixes were applied to the source org in order to make the deployment successful. A lot of time would be saved if we had the option to compare the source org to a cached copy of the target org. In this case, the source org was finishing very fast, especially when we used the local file comparison.

    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

    0 comments  ·  New feature  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Ability to upload Deployment Checklist instead of manually adding All components

    For every release, we have at least 700-1500 or more components to be deployed and adding all those one by one into gearset is a lot of manual effort which might sometimes not be entirely accurate. It would be great if there is an option where we can upload an excel or csv with all the component names and gearset would just create the package for you. It would save a lot of time and effort and reduce manual errors.

    12 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. Autodeploy on git branch a successfully manual deployment on org

    When a developper deploy a new feature on a sandbox it will be perfect if the deployment can be auto deploy on a branch git (and copy the deployement note, etc).

    Today I use a CI job backup on the sandbox but we lost the deployment comment + the updates granulartity.

    We could use also the "Clone Button" on the result deployment page but it's lost time to relaunch the comparison and the different step etc while we want exactly replicate 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)
  19. When validation fails, allow option to automatically remove metadata from deployment that was causing failure

    It's not convenient when a validation fails, to then download the excel file of the the validation errors, view in separately form Gearset, and then go through the list of metadata I'm trying to deploy and try to uncheck each one that failed the validation. It would be nice if Gearset did that for me.

    14 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. Add an option to disable deploying the email to case settings in Case.settings

    This will allow to deploy Case.settings without getting this deploy error:
    EmailToCaseRoutingAddress[Info]: emailServicesAddress is a read only field and cannot be changed

    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)
  • Don't see your idea?

Feedback and Knowledge Base