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. Add a link to open the deployment when a change is being promoted

    The pipeline view only shows that a deployment is "running" after promoting a change. It would be useful to have a link to the deployment job and be able to view the deployment status in gearset.

    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)
  2. Mobile Support

    Support mobile devices.

    The CSS Used for the Pipeline Environment popover prevents the browser from scrolling horizontally. You can try this be logging into Gearset on your phone's browser or by narrowing the browser width on your desktop.

    1. I want to deploy from my phone.
    2. I want to monitor PRs from my phone.
    3. I want to browse my Scheduled Jobs and Monitoring Jobs.
    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. Creating branch names from JIRA summaries can cause very long path names

    Gearset automatically creates a branch name from JIRA summaries. Windows paths are limited to 260 characters.

    error: cannot lock ref 'refs/remotes/origin/gs-pipeline/portal/SFBUS-33389/Update-Include-in-Export-formula-on-the-Intake-Criterio
    n-object-to-prevent-Intake-Tasks-and-Intake-Document-Checklists-from-pulling-when-associated-to-a-process-that-is-not-included-in-
    the-export-stage': Unable to create 'C:/Users/E19187/Repos/salesforce/.git/refs/remotes/origin/gs-pipeline/portal/SFBUS-33389/Update-Include-in-Export-formula-on-the-Intake-Criterion-object-to-prevent-Intake-Tasks-and-Intake-Document-Checklists-from-pulling-when-associated-to-a-process-that-is-not-included-in-the-export-stage.lock': Filename too long

    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)
  4. Add a notes field to environment variables to contain the scenarios it's addressing.

    For example, the RegEx allows finding of many different patterns that can all be handled by a single regular expression. Down the road it's less obvious which situations the regex was intended for. Having a simple notes field could be quite helpful.

    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)
  5. Add a notes field to environment variables to contain the scenarios it's addressing.

    For example, the RegEx allows finding of many different patterns that can all be handled by a single regular expression. Down the road it's less obvious which situations the regex was intended for. Having a simple notes field could be quite helpful.

    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. Restore feature branch when a mid-flight promotion branch is restored

    Have just experienced a scenario where closing a PR that is mid-flight in the pipeline caused the promotion branch and underlying feature branch to be deleted. So far, so good in terms of expected behaviour due to my pipeline settings. However, after restoring the promotion branch in order to reopen the PR and promote it in the pipeline, the next environment on the pipeline did not then show the change. This, I believe, was because restoring the promotion branch DID NOT restore the feature branch. Therefore there was no source to create a new promotion branch from in order to…

    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)
  7. Create a mass back propagation button

    Its very time consuming to have to back propagate one by one to each org. Please create a mass back propagation button.

    Also when back propagating where more than one connection to an org exists for instance our techdebt org has several admin connections and I have to hit update on all of them. Make the back propagation smart enough to know that it only needs one update rather than on each connection to the same 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  ·  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. Feedback Search Bar

    On the Feedback page place the Search bar at the top. Its odd that it sits at the bottom of the right panel

    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)
  9. Grouping more than five sandboxes should not hide them

    When grouping sandboxes, having more than 5 in a single group adds a scrollbar, and hides any additional sandboxes added to the group. This decreases visibility into sandbox status. I missed that there were several sandboxes that were very out of date simply because I couldn't see them on the pipeline. All sandboxes on the pipeline should be visible for visibility.

    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. Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to m

    Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to mask our homeowner records in Account and Contact. We do not want to mask our dealer records. If we could limit the records that are being masked by using record types, this would enable us to use your solution. Thanks!

    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. Add to Org Explorer the ability to search text within thing like Flows and Email Templates

    In addition to being able to search on the name. It would be helpful to also be able to search text within things like Flows and Email Templates. Like if you have the subject of the email template, but not the name of it to help find it.

    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)
  12. Allow backup job permissions to be control by Roles

    Backup permissions are separate from the Roles, causing duplicate permission maintenance. Please allow backups to use Roles instead

    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  ·  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. Pipeline Notification for Metadata filter for Missing components

    If I am committing some code via pipeline, in my feature branch that includes a metadata not present in my current CI Job filter, Can I get notified from Gearset that commited/merged metadata not present in the CI Job Filter?

    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 an account setting to "Mute Live Chat"

    As an experienced Gearset user I'd like to mute the live chat so the pop-up notifications don't block buttons. Pop-up notifications have been rather disruptive.
    In particular:
    after selecting two orgs for a large compare operation, I try click "Compare", and walk away while the comparison runs.
    When I return to my computer, I discover that the compare never initialized, and it turns out that although I could see and click the button "Compare", it was behind a live-chat pop-up "Hi David,...", and the button would NOT execute until I closed the live chat pop-up (x) button.

    I'm experiencing an…

    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  ·  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)
  15. Ability to "Hide" Sandbox Groups on Pipeline Page

    In the Pipelines page, it would be very helpful if we had the ability to "hide" entire sandbox groups from view. This would make it much easier to quickly find and focus on the environments that are relevant to the logged-in user.

    Ideally, this "hidden group" setting would persist across logins and page refreshes, similar to how the "collapse group" feature currently works.

    I'm sure an "unhide groups" feature will be needed with this as well, in case a previously hidden group becomes relevant 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  ·  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. Allow Archive Notifications for both successful and failed runs

    Currently, when an archiving policy runs, you can send out a notification if a run has been successful or a notification when a run has failed. I cannot see a way to have both notification types as I would like to see at a glance how many records have been archived in each run, but I also need to know when it fails with permission issues after deployments or major releases. I do not go into the Archive section every day.

    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)
  17. Provide a Model Context Protocol (MCP) for Gearset

    It would be really helpful if there were a Model Context Protocol (MCP) server for Gearset. As companies are adopting AI LLM tools as part of their day-to-day work, integrations with tools like Gearset become a necessity and MCPs are becoming more and more available, even Salesforce has support now (https://developer.salesforce.com/blogs/2025/06/introducing-mcp-support-across-salesforce).

    As an example, we use Claude Deskop connected with an Azure DevOps MCP (https://github.com/microsoft/azure-devops-mcp) to connect to ADO. Claude helps assess priorities, organize releases, check for duplicate issues, and even identify issues that have fallen through the cracks.

    Expanding on that, it would be really…

    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)
  18. add support for lightning types (LightningTypeBundle)

    Add support for lightning types (LightningTypeBundle)

    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. Display the developer who opened the PR throughout the entire pipeline flow.

    As a Release Manager, I have difficulties identifying the developer responsible for the PR.

    The developer's name only appears when they open the PR at the beginning of the process, and in the following stages, it shows the system user's name from git that Gearset uses to open the PRs up to production.

    Since I need to easily know who opened the PR during the release creation, I have to open the feature card to find the developer. ...

    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)
  20. View Deployment Summary from Pipelines

    My team develops in siloed dev orgs. Once a feature is complete, we create a PR against an integration environment.

    This triggers a test suite run in the target org and a peer code review. This process works well for Apex. However, admins on our team build automations in Flow, which are nearly impossible to review in GitHub due to the complexity of the XML.

    To address this, we’ve been using Gearset’s Flow Navigator for Flow code reviews. Previously, it only took a couple of clicks to reach the Deployment Summary screen, and the Flow visualization made reviews much easier.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 67 68
  • Don't see your idea?

Feedback and Knowledge Base