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

1361 results found

  1. Add Pre/Post Deployment steps for Data deployments

    Some data deployments require manual steps pre and or post deployment.

    Scenario we had was that a rule for whatever reason couldn't be turned off by GS so I had to manually switch it off or the deployment failed then back on after it deployed,

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Audit changes to the "Require issue tracking" setting

    As a result of a query by our auditors it would be helpful to have changes to the 'Require issue tracking' deployment setting audited. They are concerned that a team-owner could alter this to perform a deployment then reinstate it, resulting in change deployment without tracking.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Audit changes to the "Require issue tracking" setting

    As a result of a query by our auditors it would be helpful to have changes to the 'Require issue tracking' deployment setting audited. They are concerned that a team-owner could alter this to perform a deployment then reinstate it, resulting in change deployment without tracking.

    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

    1 comment  ·  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)
  4. Show doesRequireRecordChangedToMeetCriteria on Flow Navigator

    The doesRequireRecordChangedToMeetCriteria toggle on flow Decisions doesn't show on Flow Navigator, making it harder to check for issues on builds when using the comparison tool.

    doesRequireRecordChangedToMeetCriteria should show in the flow navigator, same as the rest of the decision configuration.

    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

    5 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)
  5. Fix comparison default date range

    1. Click new compare and deploy
    2. Select a source and target.
    3. Notice the date range says "Today" but DON'T change it.
    4. Click Compare
    5. Notice the date range now says "All Time"

    Repeat...
    1. Click new compare and deploy
    2. Select a source and target.
    3. Notice the date range says "Today"
    4. Change the date range to anything else
    5. Change the date range back to "Today"
    6. Click Compare
    7. Notice the date range now says "Today"

    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)
  6. Fix pre/post deployment steps from disappearing.

    1. Add Pre or Post deployment step
    2. Click "Specific environments only"
    3. Click the "x" to remove all the environments Notice, the entire "Environments to run against" section disappears To get it back you have to cancel, and do it 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

    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)
  7. Make pre/post deployment steps conditional on developer sandboxes.

    Pre/Post deployment notes can be set to pertains to various static environments but they always apply to sandboxes after a back deploy. This should be conditional-- most of the time I only set them applicable to prod and they aren't applicable to developer sandboxes.

    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  ·  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)
  8. Add Omnistudio Features to Scratch Org Features list

    When using the 'Create new scratch org' screen the following features are not available in the 'Scratch Org features' list

    OmnistudioMetadata
    OmnistudioRuntime
    OmnistudioDesigner

    These are available features according to the Salesforce documentation

    https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file_config_values.htm#so_omnistudiodesigner

    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)
  9. Pull Request Changed Items View Fix

    When viewing the items in a pull request in the 'Changes in this PR' section of the pipeline you only see the file name.

    I would like to see something more similar to an actual comparison view where you have a tab with one column for the name and then another for metadata type.

    Having just the full file name does not give me that instant information I need, especially when its a long file name and the type runs off the page never to be seen unless you hover over the file.

    Converting to a table format might also…

    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)
  10. Allow IN Operator for Data Deployments

    When filtering for specific records with ID's, would be handy to have an IN operator for record selection.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Problem Analyzer while building the deployment

    Surface problems with building the deployment to allow users the correct in 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)
  12. Feature that allows users to post Deployment information to custom object in Salesforce

    Gearset has feature to allow users to send depolyment information to Jira. Provide the ability to do the same to a custom object in Salesforce.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Please add 'Type' and 'Priority' field from Jira to Reporting API.

    In the absence of 'Type' and 'Priority' field from Jira in Reporting API, it become significantly challenging to report on Cange Failure Rate and Mean Time To Resotre and rely on either on the Jira title or description, which is again a heavy lifting in order draw the report.

    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)
  14. add the ability to set a Profile Picture

    Honestly I'm actually surprised it's not possible to set an avatar at the moment, it seems a pretty basic feature in today's online world!

    As a neurodivergent team, we want to increase accessibility by being able to distinguish our team members within the platform faster and more easily, so that we can increase our productivity.

    It's simply easier to recognise my user in GS if it's "the one with the funny cat" instead of just my initials. Similarly, since we have team members with the same initials that also makes it harder to distinguish them in GearSet since their profile…

    8 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. Force API update for deployment

    Please provide the ability to force API versions for deployments.

    Allow the administrator to place an API version in a setting and when a deployment is validated or attempted deploy if the API version is the value or below then do not allow the validation or deployment.

    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)
  16. Feature Request: Deployment Blocking Based on Daily Unit Test Job Status

    Currently, Gearset lacks a feature to block deployment CI jobs to the respective environments when the associated daily unit test job fails. Implementing this feature would be advantageous in ensuring that appropriate testing quality gates are established to prevent changes from being deployed in the event of test failures. This enhancement would significantly improve our deployment integrity and testing processes.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Trigger CI Jobs on Gearset deployments

    When setting up a CI Job originating from SFDC, we only have the option to trigger the job based on a time interval. Which makes sense since there are no events to subscribe to in SF for this.

    But, I think it'd be helpful to be able to trigger a job to run on the completion of another Gearset deployment. This would be useful for automating the addition of metadata items like fields or layouts into source control, which are less-than-fun to create as xml files.

    So rather than running such a job every 1hr, we'd ideally be able 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)
  18. Feature Request: API Endpoint & Webhook for Validation Errors

    I hope you’re doing well.

    I’d like to propose a feature enhancement for Gearset’s API that would greatly improve integration and visibility across systems like Slack, GitHub, and Jira.

    Feature Request:
    • API Endpoint:
    Expose the existing endpoint as part of the Gearset API: https://us.app.gearset.com/api/validation/started/{jobId}/result that returns specific error messages for failed components after a validation attempt.
    This would allow us to programmatically retrieve validation outcomes and integrate them into other systems for better tracking and visibility.

    Webhook Support (Bonus Feature):
    Even better, adding webhook functionality to push validation results directly to external systems (e.g., Slack) would streamline our workflow.…

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Visibility settings for 'Shared Sandboxes' in the gearset pipeline

    Currently, Gearset only supports the binary visibility settings for sandboxes; either the developer could see his/her sandbox or everyone's sandbox. But in the case of a 'Shared Sandbox,' there is no ability to give visibility access only to a specific subset of users in the pipeline.

    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

    1 comment  ·  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)
  20. Please add support for GenAI objects

    Backups are currently failing when GenAI metadata objects are selected. Please add support so that we can backup agentforce related metadata.

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

Feedback and Knowledge Base