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.
1468 results found
-
Option to Export Full Comparison (Including JSON Metadata Differences)
Currently, when exporting a comparison from Gearset, the CSV includes a list of all items from the comparison. However, the export does not include the JSON data that represents the metadata differences between environments.
It would be extremely useful to have the option to export the full comparison, including the detailed JSON metadata diff.
Use case:
Our team is exploring ways to automatically generate changelogs whenever we make deployments. Being able to export the JSON comparison data would allow us to feed that information into an AI agent to generate a structured, human-readable changelog.Proposed enhancement:
Add an option to…
6 votes -
Automatically create a ServiceNow change request when a release has been created
We use ServiceNow for a change management processes. All changes to a production system require a change request. We release changes to production multiple times a week and even multiple times a day so this manual creation of ServiceNow change requests becomes tedious. It would be great is gearset could provide a way to automatically create a ServiceNow change request and auto-populate the description in servicenow with a list of changes included in the gearset release. It could be taken further like default assignment groups etc, but just creating a change request with the gearset changes and leaving it in…
2 votes -
Darkmode option
It would be really helpful having a dark mode of gearset UI. A big number of devs prefer dark mode over bright mode. Since gearset is a tool mainly used by devs, would be good to give to devs the option to customize their UI.
22 votes -
Change the build view in Bitbucket Pull Requests
In the Pull Requests build checks summary on bitbucket, I’d like the view to only display builds that are failing for the current pull request. Right now it shows what is failing for the repo at large.
1 vote -
Migrate a user to different login method without new acount or allow same user with multiple login methods
For each login method a user gets assigned a new account and has to re-setup all of their person connections. Please allow an Enterprise Gearset Admin (Owner) to update or migrate a user from one login method to another. Or allow the user to authenticate using any of the allowed methods without creating a new user account.
1 vote -
From the gearset pipeline view, i wish there an option to export all the pull-requests including the respective git branches in a csv or .xl
From the gearset pipeline view, i wish there an option to export all the pull-requests including the respective git branches in a csv or .xlsx format
1 vote -
Allow deploying fixes / linking work to closed Jira tickets without reopening them
Currently, deploying a fix related to a closed ticket requires reopening it, which triggers unnecessary notifications to the reporter.
It would be helpful to allow linking or deploying fixes to closed tickets without changing their status, or alternatively make it easier to search and reference closed tickets.2 votes -
Pipeline: a more selective developer sandbox alignment
In the pipeline, let's say there are more developer sandboxes and a feature-branch is created from one of them and merged until the main branch.
At this point, only the other developer sandboxes must be aligned from main, there's no need to align the one where the feature-branch was created from.
Therefore, the pipeline should show the symbol 'need of alignment' only on the other sandboxes.1 vote -
license
Update Audit Report to include License assigned. This is on the user export list, but missing from the Audit. Role(s) assigned is also needed (idea already in the list for that one).
1 vote -
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…
7 votes -
Limit file size for download of Data backup Snapshots
When trying to pull a complete snapshot of a previous history databackup (including files) the file generated can be quite large (> 500GB). This is difficult to download using traditional methods.
Need a way to have the file(s) broken down into small chucks (500mb to 1gb in size) [i.e batched] so thats is more manageable to download.1 vote -
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.
3 votes -
Allow Metadata Filters to be Version Controlled
Represent a metadata filter as a file (e.g., JSON/YAML/XML) that can live in the repository, similar to a package.xml. When configuring a compare/deploy, Gearset would automatically use this file if it exists in the selected repo. This would allow the filter configuration to be version controlled, which would be especially useful for CI jobs, as filters play a critical role there.
3 votes -
Notifications/Reminders for Promotion Pre/Post-Deployment Steps
When a deployment is waiting on a pre or post deploy step, send a Slack notification or email. These are easy to forget about (or they are completed, but the dev forgets to check them off). Even better would be if the Slack message tagged or emailed the user it was waiting on.
2 votes -
Ability to Select and Merge Specific Changes in Lightning Components and Flows
We are using Gearset to compare and merge changes in Lightning and Aura components, as well as Salesforce Flows. While the tool works well overall, we’ve noticed that it currently lacks the ability to select and move specific changes during a merge. Instead, it requires replacing the entire file, which isn’t ideal in many cases.
It would be extremely helpful if Gearset could allow selective merging of specific lines or sections—similar to how it works for Apex classes. This feature would greatly improve control and efficiency when working with Flows and Lightning components.
Thanks for considering this enhancement!
10 votes -
Conflict Resolution Comments
It would be great if there were a way to leave notes or comments for each specific action I take or selection I make during conflict resolution in Gearset Pipelines. This would really help other people understand the reasoning and history behind conflict resolution activity for future reference.
2 votes -
Allow for Simplify Differences to be performed on metadata type before showing it as "different"
Currently, Gearset performs a "Simplify Differences" on Clean data service and
Connected app before reporting these metadata types as "Changed" in the comparison results.There are other metadata types, such as "Custom field" that sometimes show up as "Changed" in comparisons because the internal order of some of the tags are different in a sandbox vs production. Re-deploying these files from one environment to the other does not "fix" these differences. Gearset provides a "Simplify Differences" toggle in the UI that shows there is no effective difference with the file.
It would be nice to provide a configuration toggle for…
3 votes -
export
Ability to queue up multiple exports. As part of internal processes we are looking to download the final Org snapshots from the end of FY25. We have 10 prod orgs being backed up. Seems like we can only have one export job running at a time.
Please add the ability to queue up the backups.1 vote -
Allow more than one top level object for seeding.
The latest Sandbox Seeding tool requires a single top-level object. This isn't useful for us as we have multiple entry workflows. I would like to be able to have multiple.
As an example
We have users who work on Cases via Service Cloud. Almost all of those Cases have an Account, but not All.
We have users who work on Orders. All of those orders have Accounts but few have Cases.
We have users who work on OurCustomObject. All of those OCOs have Orders and Accounts but not all Orders or Accounts have OCOs.1 vote -
Auto merge of PRs
Once the validation process is successfully completed for the respective PR, it would be very helpful to have an option for automatic merge and deployment. This would streamline the release process and reduce manual steps.
Additionally, it would be great if we could have control at the org level to enable or disable auto merge functionality. This way, teams can decide whether they want to use auto merge based on their workflow preferences or organizational policies.
Thank you for considering these enhancements!
10 votes
- Don't see your idea?