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. Apply masking of certain data across backups GDPR compliance

    It would be great if records that were marked with certain GDPR attributes, possibly 'GDPR Removal = TRUE' that the backups could apply arbitrary data masking across all historical backups for email and phone number fields

    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  ·  Data backup  ·  Flag idea as inappropriate…  ·  Admin →
  2. Show the name of the draft I am working on

    Would be nice to see the name of the draft I'm working on while I'm working on it. Oftentimes working on multiple things at once, this can get really confusing.

    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  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Rename drafts after they're created

    It would be really nice to be able to rename drafts after they've been created. Sometimes users will name things differently, and it would be nice to be able to clean this up.

    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  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  4. I would like the ability to change filtered metadata to their API names

    I recently had an internal business conversation to clarify what would and wouldn't be included in our new CI/CD process leveraging gearset to push to orgs. When we had this conversation we used the Metadata API names to discuss and then when I went to implement it in Gearset I saw that the filters are actually some translated 'friendly' names.
    This is of course fine for most use cases, but it made it really difficult to make sure nothing is being missed when setting up the CI/CD filter type.

    I would kindly ask that you implement some switch to allow…

    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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  5. Ability to cherry pick changes in a file

    When comparing changes between a source org and a target org for a given file/metadata component, it will be great to have the ability to choose which change(s) should be promoted from the source org to the target org.

    Presently, it's an all-or-nothing scenario i.e. either one deploys all the changes to a given file from source to target or deploys none. As a workaround, we cherry pick changes to a file using VSCode and then deploy to the target org using VSCode –– which is the exception to our "all metadata changes must be deployed through Gearset" policy.

    Adding…

    4 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

  6. Unable to import/export translations using .stf file using greaset

    Currently gearset allows to deploy translations from one org to another org, however we do not have an option to do the translations using .stf file /excel for the fisrt time in any one of the org

    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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add additional controls to Monitor

    Hello Gearset,
    We are exploring using the "Monitoring" functionality to audit our Salesforce production metadata changes for our IT Controls. It looked promising until we found out that anyone on the team can edit any monitor job setting, which creates a loophole in the controls that we can't monitor the monitor.
    So I'm curious to learn from Gearset whether any of the following can be done/requested:
    * Can we limit the Monitor jobs to only be editable by the person who created it?
    * Can we show either an audit history or LastModifedBy/LastModifiedTime of the Monitor job?
    * If the…

    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

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  8. Limit Connections creation

    Currently there is no feature to prevent users in creating their own connections within Gearset.

    We need users to follow the permission that was setup on the shared connection. We have only 2 users that have the approval to deploy code from a sandbox to production. As they can set up their own connections then this bypasses our restriction

    Having a permission only available to the Enterprise user or a user approved to create connections and delegate access would prevent the bypass of access permissions

    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

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  9. Display API name and friendly name of permissions within Analyzer messages

    when Gearset Analyzer tells you that you should consider removing a permission from the deployment, it displays the API name of the permission but often this doesn't tell you what item in the Setup UX you need to check on

    example:

    ContentHubUser is actually the permission for Files Connect Cloud My suggestion is that Gearset take advantage of this resource http://www.fishofprey.com/2020/10/mappings-between-salesforce-permission.html and display both the API name and the UX name in parens - such as :
    ContentHubUser (Files Connect Cloud)

    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  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  10. enable data deployment template merge

    It is currently possible to select an existing template and add new objects and data deployment logic into it then save as a new template. It would save time to enable the selection of 2 existing templates and merge them into a single one.

    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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Run all tests only when have apex classes in the package

    Hello,
    I want suggest an option to avoid run unit tests when no have apex class in the package.
    And run all tests when have any apex class in the package.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  12. Modify files during deployment process

    In Salesforce, if you add an image to a PathAssistant, it hard codes the sandbox URL in the metadata. This causes failures when you then try to deploy that item to the next environment. My idea is that a feature is added that would allow some sort of find/replace logic that's applied prior to the CI compare. Something like:
    File: Enter the name of the package file
    Search Text: The text and/or regex string to search the file for
    Replacement Text: The text to replace found the text with

    In this way, it would modify the source file prior 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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  13. Archive or hide Automation jobs

    On each of the Automation dashboard views (Monitoring, Unit testing, Continuous integration) it would be nice to have a way to archive or hide job. Often times previously setup jobs that are not active but would be good to keep for historical reference can clutter the dashboard.

    5 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

    2 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  14. Need to have JIRA integration with Data Deployments

    Need to have JIRA integration with Data Deployments which will improve the process and allign it with meta data deployments

    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  ·  Data deployment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add Salesforce ID to Export History button

    Can you add the Salesforce ID to the Export History button for reconciliation purpose.
    We currently have to manually match the Salesforce ID in Gearset with the Salesforce ID on the Salesforce Deployment Status page to get the reference between the source ticket in Jira and the deployed change for compliance purpose which is a time consuming process.

    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  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add Apex Page Permissions to Repo Dependency Cleaner Functionality

    It seems based on the below doc

    https://docs.gearset.com/en/articles/3624846-what-does-gearset-s-repo-dependency-cleaner-do

    That the repo cleaner will remove permission references related to the following deleted items:

    Apex Classes
    Tabs
    Apps
    Object Permissions
    Field Permissions

    Missing from that list is Apex Pages. It'd be great to have that included to clean up references to the deleted page without having to re-run a 2nd comparison for source control.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  17. Validation Job to validate feature/* branch by scratch org creation

    The idea is to validate feature branches in repo. For doing this it's necessary to allow specifying source branch by pattern (like feature/*) in "Add CI validation job" menu. The validation should check whether the code breaks the scratch org creation or not. This is valuable due to fragility of scratch org creation process (sfdx force:source:push).

    4 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  ·  Flag idea as inappropriate…  ·  Admin →
  18. Scratch orgs with packages with InstallationKeys fails to install in CI

    When creating a new scratch org you have the option of specifying the package and the installation key. This option is not available in a CI job to scratch org target scenario.

    When there are dependencies specified in the sfdx-project.json file that requires an installation key the CI job run fails when the CI tries to install them.

    There needs to be a way to specify the installation key, either by a custom JSON field in the sfdx-project.json, or on the CI job itself.

    5 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  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  19. Checkboxes to delete multiple packages/validations/deployments at a time

    Hi - feature request:
    Checkboxes on the validated packages (and probably others) screen so that I can delete validated packages more quickly. One by one is a big pain, and it probably uses your storage... and it definitely clutters our workspace.
    Thanks!

    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  ·  Flag idea as inappropriate…  ·  Admin →
  20. Hide irrelevant comparison types/components

    After selecting the source org and viewing the metadata comparison filters, there should be an option to only show those types that contain data (the ones that have a number in parentheses). Or in other words... the ability to hide anything that isn't being used.

    This would make it much faster to create new comparisons (or troubleshoot existing ones).

    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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
1 2 5 7 9 39 40
  • Don't see your idea?

Feedback and Knowledge Base