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

1251 results found

  1. Ability to change Formula Fields to other Field Types

    Gearset doesn't help with one of the most common deployment headaches: changing a formula field to a non-formula field type. It's still a nightmare even with Gearset.

    What would be awesome would be if you had a "Change Field Type Wizard" where we could say FormulaField1 needs to become TextField1 and it would do multiple deployments to accomplish the changeover:
    - get components
    - deploy temp field of new type AND update all existing components to reference the temp field instead of the formula field
    - deploy delete of formula field
    - deploy text field in place of the old…

    3 votes
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?
  2. call webhook with scheduled deployment

    We would like Gearset to call a webhook when a scheduled deployment completes. The message to the webhook should pass a message with the org name, UTC datetime, the deployment friendly name, URL of Gearset deployment results and a status field with 'succeeded' or 'failed'

    3 votes
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?
  3. Provide integration with WebexTeams

    We moved from Slack to WebexTeams and have lost the ability to post deployment notifications from Gearset. Here's an article about Webex Bots: https://developer.webex.com/docs/bots.

    3 votes
    How important is this to you?
  4. Find/Replace before deployment

    Allow a basic find/replace to run against files before final deployment.
    Examples: a username that would work in the sandbox that does not exist in production and we need to change it. Or deploying to a packaging org required a modification due to various namespace issues. Other tools have a means to do this in one way or another.

    3 votes
    How important is this to you?
  5. Clone Package - keep Tests list

    It would be great if when cloning a deployment, it can keep the tests which got performed in the original deployment. Right now, we need to keep a list of the tests which ran on a doc on the side.

    3 votes
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?
  6. 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
    How important is this to you?
  7. 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
    How important is this to you?
  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
    How important is this to you?
  9. 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
    How important is this to you?
  10. Ability to update value of Reference field for a data deployment

    "Select reference fields to deploy"

    Ability to edit the value for the target deployment data for the reference field instead of searching for the match on the Target.

    Ex. Loading Opportunities from a Source to a Target that contains 5 different record types, but when uploaded to the Target we specify the recordtypeid to one that matches a recordtypeid on the Target for the entire data load.

    Similar to how the Owner reference can ignore the Target's users and default to the running user of the data deployment.

    3 votes
    How important is this to you?
  11. Ability to have Tests to Run during Validation to default to Unchecked all

    Ability to have Tests to Run during Validation to default to Unchecked all vs all checked (even before they finish loading into the component). We often validate with only a few tests or predefined group of test classes that we input into 'Specify Tests to run' and if a user inputs those test classes in the text area before all the Tests populate above in the list, it will include all of the ones available. It defaults to checked all and they need to remember to uncheck them or to wait for them all to load which can take awhile…

    3 votes
    2 comments  ·  Testing  ·  Admin →
    How important is this to you?
  12. 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
    How important is this to you?
  13. 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
    How important is this to you?
  14. display meta data filter used on deployment report

    It would be useful to see the meta data filter used on the deployment successful report

    3 votes
    How important is this to you?
  15. 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
    How important is this to you?
  16. Eliminate unnecessary XML reformatting in git

    Currently, when gearset deploys XML to git, it seems to run it through a reformatter, which creates superfluous changes in git. These changes cause extremely large deltas, which are hard to read, increase the difficulty of merges and the likelihood of conflicts, and make working with any other metadata tooling (like SFDX) difficult.

    For example, here is part of a delta gearset commited for a profile.xml:
    diff --git a/force-app/main/default/profiles/Commissions.profile-meta.xml b/force-app/main/default/profiles/Commissions.profile-meta.xml
    index 8b11e6b7..3d640a50 100644
    --- a/force-app/main/default/profiles/Commissions.profile-meta.xml
    +++ b/force-app/main/default/profiles/Commissions.profile-meta.xml
    @@ -1,10 +1,27 @@
    -<?xml version="1.0" encoding="UTF-8"?>
    -<Profile xmlns="http://soap.sforce.com/2006/04/metadata">
    +<?xml version="1.0" encoding="utf-8"?><Profile xmlns="http://soap.sforce.com/2006/04/metadata">
    + <custom>true</custom>
    + <profileActionOverrides>
    + <actionName>Tab</actionName>

    Note that it lowercased…

    3 votes
    How important is this to you?
  17. Give users the ability to update field/object permissions for specific profiles only

    The issue is, when promoting from one org to another and changing either Custom Object Permissions or Custom Field Permissions and if more than the profile you want has been changed, the extra profile changes get promoted anyway. So we need a way to control which profiles get applied when promoting field and object level security.

    3 votes
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?
  18. 3 votes
    0 comments  ·  Testing  ·  Admin →
    How important is this to you?
  19. Queue Deployments

    Current State:

    A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org

    1st Dev deploys work to .dev

    2nd Dev deployment fails because org is locked

    Idea:

    A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org

    1st Dev deploys work to .dev

    2nd Dev deployment is queued up, 2nd Dev will be notified via email/browser when queued deployment has started

    3 votes
    How important is this to you?
  20. add the ability to run static code analysis against an org or source control, simply click refresh button to re-run it and see results

    This will give you a "run code analysis -> see results -> fix issues -> push to source control (or an org) -> repeat" workflow.

    3 votes
    How important is this to you?
  • Don't see your idea?

Feedback and Knowledge Base