1430 results found

1. Ability to bulk download filtered records from Archived Data

   We Archived over 50GB of data and business wanted to get a list of leads from the last 6 months. There were over 30,000 records and I had to click thru every page, let the page load before I could download them all. There were over 60 pages to click thru. One click button to download them all would a time saver.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Data backup  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Add a feature to ignore queue members when deploying queues

   When deploying Queues with Gearset the members section is automatically included and the member list is deployed to the target org. Gearset has a suggested fix to sync the queue members with the target environment but it doesn't always work.

   Salesforce supports deploying queues with an empty list of users as queue members are more like data than metadata I suggest a feature toggle in Gearset where the users section of the queue is ignored for deployments to preserve the user list in the destination org.
   Our company and many others probably maintain the queue users directly in production as it's done with public group membership.

   Here is an excerpt of the xml and what to remove to preserve the queue members in the target org.

   <?xml version="1.0" encoding="UTF-8"?>
   <Queue xmlns="http://soap.sforce.com/2006/04/metadata">
   <doesSendEmailToMembers>false</doesSendEmailToMembers>
   <name>QueueNameTest</name>
   <!-- Remove from here
   <queueMembers>
   <users>
   <user>bla@blabla.com</user>
   </users>
   </queueMembers>
   Remove to here-->
   <queueRoutingConfig>Test</queueRoutingConfig>
   <queueSobject>
   <sobjectType>Case</sobjectType>
   </queueSobject>
   <queueSobject>
   <sobjectType>LiveChatTranscript</sobjectType>
   </queueSobject>
   </Queue>

   When deploying Queues with Gearset the members section is automatically included and the member list is deployed to the target org. Gearset has a suggested fix to sync the queue members with the target environment but it doesn't always work.

   Salesforce supports deploying queues with an empty list of users as queue members are more like data than metadata I suggest a feature toggle in Gearset where the users section of the queue is ignored for deployments to preserve the user list in the destination org.
   Our company and many others probably maintain the queue users directly in production as… more

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Notification on job start, end with the Salesforce deployment/validation Id

   When a new Job is created, it would be great to have the notification/webhook sent on start and end the job, that way, we have a monitoring outside of the Gearset on it. As well as this, to be able to build soe automations based on it

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Monitoring and reporting  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Auto-cancel the old CI/CD process on new commit pushes.

   When a validation is runnnig based on PR changes, it would be great to cancel old validation job on gearset, as well as the validation on the salesforce on new commit pushes. That way, redundant jobs are not stacking to be validated and increase the CI/CD flow when multiple PRs are there

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployment automation  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. External Client App

   I have been testing out the ability to promote External Client Apps through a pipeline. I found that if I include the 5 files (.eca, .ecaGlblOauth, .ecaOauthPlcy, .ecaOauth, and .ecaPlcy) that define the ECA, I receive an error of 'We couldn't update your OAuth Link...'.

   But, if I edit the .ecaOauth file and remove the oauthLink tag/value then the promotion succeeds. This is an optional tag is set from the source org, and can be removed before promoting. It would be great if this was handled automatically, maybe with the problem analysis tool.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployment automation  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Compare UI feedback after large salesforce project

   1. Preserve location when switching between new/changed/deleted views. When reviewing a compare with hundreds of components, it's annoying to have to re-scroll when returning to a view. We could filter the lists, but that often means less scrolling, not no scrolling.
   2. Make the XML view sticky. I'm old school, but after I click on XML view 5 times, 10 times, 20 times, my default should be switched to XML.
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Comparisons and difference visualization  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Using GitHub Apps to Replace Service Account for Team Shared Connection

   Problem Statement / Current Situation:

   For enterprise security compliance, organizations are moving to a model where all third-party integrations must use pure application-based identities (like GitHub Apps) instead of user-based accounts.

   Currently, Gearset's CI/CD jobs require a "Team Shared Connection," (https://docs.gearset.com/en/articles/8455568-team-shared-source-control-connections) which uses a combination of a GitHub App for authorization and a separate GitHub "service account" user for commit attribution. While this is a functional workaround, it still forces us to create, manage, and secure a user entity in GitHub. This goes against modern security principles that aim to eliminate the management of all user credentials, even for service accounts.

   Proposed Solution:

   We propose that Gearset enhance its GitHub integration to allow a GitHub App to be used as a complete, standalone identity for CI/CD operations.

   This would mean that when a CI job runs a merge, the author of the merge commit would be the GitHub App itself, not a separate service account user. This is an emerging best practice in the industry, as a GitHub App can have its own identity and be an actor within the system. As security expert Josh-ops notes in his detailed article on the subject, this provides a more secure and streamlined approach by "moving the identity from a user to the application itself."

   Problem Statement / Current Situation:

   For enterprise security compliance, organizations are moving to a model where all third-party integrations must use pure application-based identities (like GitHub Apps) instead of user-based accounts.

   Currently, Gearset's CI/CD jobs require a "Team Shared Connection," (https://docs.gearset.com/en/articles/8455568-team-shared-source-control-connections) which uses a combination of a GitHub App for authorization and a separate GitHub "service account" user for commit attribution. While this is a functional workaround, it still forces us to create, manage, and secure a user entity in GitHub. This goes against modern security principles that aim to eliminate the management of all user credentials, even… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Add originating Sandbox(es) as a PR comment

   It would be awesome to be able to see what Sandbox/org each commit (and thus PR) originated from. There is not many places to add the information to VCS as you can add comments only in the PR stage, but could you for example add comment to PR when promoting with the list of all commits + their origins?

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Add Metadata Filter Requirements/dependencies for Deploying Product Records via CPQ

   It would be really helpful if Gearset provided a dedicated document that clearly outlines all metadata filters required to successfully deploy Product records through Salesforce CPQ. Having a reference would make deployments more predictable, reduce trial‑and‑error, and improve consistency across teams especially who use pipelines. Adding this documentation to the platform would streamline CPQ-related deployments and save users significant time.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Problem analysis and deployment failures  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. If a Branch fails to create in Github, display the error

    We have enabled Rulesets in Github to enforce naming conventions. If a Gearset user tries to create a branch the ruleset will block it. Gearset then displays a generic "Could not create branch X from Y. Please try again or contact support" error to the user, but the error received from Git should include the ruleset's error message.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Visual Sync Alerts for "Commit more changes" Workflow

    Summary:
    Introduce a sync indicator for features in the pipeline. This would alert users when a feature branch has received additional commits (via the "Commit more changes..." button) that have not yet been promoted to downstream environments.

    Problem:
    When an admin or developer adds metadata to an existing feature branch that is already sitting in a downstream environment (like UAT or Stage), a "parity gap" is created. Currently, the pipeline doesn't visually signal that the version in UAT is now "stale" compared to the version upstream.

    This creates a risk where a user might promote a feature from UAT to Production, forgetting that the latest commits (the "more changes") are still sitting in Dev.

    Example:
    1. Initial State: A new field is promoted from Dev → UAT.
    2. Feedback: A stakeholder in UAT notes the Help Text is incorrect.
    3. The Gap: The Admin uses "Commit more changes..." to update the help text in Dev. Now, the feature branch in Dev is "Current," but the feature in UAT is "Stale."
    4. The Risk: Without a visual warning, a Release Manager might promote the UAT version to Production, accidentally deploying the "Incorrect Help Text" because the fix was left behind in Dev.

    Proposed Solution:
    Status Flags: If "Commit more changes" is used, any downstream environment holding that feature should display a "Version Outdated" or "Update Available Upstream" badge.

    Sync Requirement: This badge persists until the new commits are promoted to that environment, ensuring the "furthest" environment always has the most recent version before a Production release.

    Resolution: The warning remains until those specific upstream changes are promoted to that environment, bringing the feature back to parity across the pipeline.

    Impact
    Currently, Gearset’s "Bug" feature handles fixes for things already in Production. This request addresses the "Pre-Prod Revision" cycle. It ensures that if a developer is actively adding to a feature branch, the Release Manager has a clear warning that the version currently being tested in UAT is no longer the "source of truth." This significantly reduces the risk of accidental stale deployments.

    Summary:
    Introduce a sync indicator for features in the pipeline. This would alert users when a feature branch has received additional commits (via the "Commit more changes..." button) that have not yet been promoted to downstream environments.

    Problem:
    When an admin or developer adds metadata to an existing feature branch that is already sitting in a downstream environment (like UAT or Stage), a "parity gap" is created. Currently, the pipeline doesn't visually signal that the version in UAT is now "stale" compared to the version upstream.

    This creates a risk where a user might promote a feature from UAT to… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. 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.
    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Hide unchanged fields on "Search" for Data Backup

    When searchin on a Data Backup and looking at the comparison between record changes, we should be able to hide any unchanged fields in the list, to be able to look at changes quickly at glance without having to scroll up and down the full field list.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Data backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Allow multiple team members to be assigned to a single sandbox on the pipeline view

    Currently a single team shared sandbox can have multiple users with delegated access. However, only one of the users can view the sandbox in a pipeline view. In order to allow multiple people to see the sandbox -

    Current solutions:
    - Add the same sandbox multiple times and assign each to the required team members
    - Or, allow all team members to see all sandboxes

    Suggested solution:
    - Allow multiple team members to be selected via the "Assign sandbox to team member" function.

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Allow specifying private email address when sending commits to github

    Github supports hiding your address in commits by using your github private address, but this requires you to specify the private address instead of your username when creating the commit. Add a user settings that allows this to be specified when making git commits so we don't have to turn this feature off when using gearset.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Quick piece of feedback, it would be great to open up records in the source and target orgs, by right clicking on the record in Compare and

    See message history with Ryan earlier today - Quick piece of feedback, it would be great to open up records in the source and target orgs, by right clicking on the record in Compare and Deploy screen
    Nazrul • 1h ago
    Do you mean, be able to open the records directly in Salesforce via a link from the compare and deploy screen?
    Ryan • 20m ago
    exactly

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Add support for Jira Service Accounts

    Jira has (finally) added Service Accounts, so that full Jira users are no longer required. Would be great to take advantage of this. For reference: https://support.atlassian.com/user-management/docs/understand-service-accounts/

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. 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 issue that was previously reported as a bug and marked as fixed, but it seems to have creeped in again, so I'm providing this as a longer term fix for the issue described in the related bug:
    https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/18993766-live-chat-button-overlays-action-button

    I hope the details help, and thank you for this fantastic product.

    Cheers!

    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… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. 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 helpful to have a Gearset MCP which Claude could connect to Gearset and look at things like deployment history, draft deployments., PRs. automation pipeline, and be able to answer questions about the status on various issues/bugs, etc, which exist on tools like ADO / JIRA, and help assess things like:
    When an issue was deployed, and to which environment.
    Or if a draft deployment includes all the metatdata/components needed to resolve the user story in ADO/JIRA. There are a lot of options!

    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… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Add Link to Comparison in Gearset to VCS PRs

    Include a direct link to the corresponding Gearset comparison in the description or as a comment to the PR in Github (or other VCS). This would greatly streamline the review process, particularly for Flows, because Gearset's flow diff viewer is the best way to review those XML changes. Without this link, reviewers must manually jump to Gearset and select the proper source and target to perform the necessary comparison.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating