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.
1400 results found
-
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/
1 vote -
Need to store the Source record ID from source to target org
When moving data from Org1 to Org2, The record ID from the source needs to be stamped in the target org in order to update that in the future, and this will be really helpful.
Thank you.
1 vote -
Change the test running options in pipelines
The options for tests in CI jobs/pipelines don't seem to offer quite what I need for sandbox deployments. Specifically, I want to be able to run all the tests when class/flow/trigger metadata is changing but no tests when tests metadata do not change.
This is possible to do when deploying to production orgs by using the "Salesforce default tests" option (see https://docs.gearset.com/en/articles/1376067-setting-apex-test-levels). But it is not possible in sandboxes.
In sandboxes, the "Salesforce default tests" option runs no tests at all which I don't want. I also don't want to run "All your tests" because if merging a branch…
1 vote -
focus
When viewing a Comparisons results and click the filter icon in the column header to filter that column, it would be nice for the focus to be automatically placed on the filter text so it can be typed directly (without having to click on the filter text field).
1 vote -
checkbox
When viewing Open Pull Requests in an environment in a pipeline, the user can click the checkbox beside the pull request thinking they have selected that pull request. Clicking the checkbox does not currently select that Pull Request in the UI. It would be nice if clicking the checkbox would also select the current Pull Request in case another function such as "Close pull request" (trashcan icon on right pane) is being selected.
It is easy to think you have selected the pull request when clicking the checkbox for it and in turn close the wrong pull request as a…
1 vote -
I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be benefic
I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be beneficial to have the option to allow a user to commit changes to a branch but block their ability to create a pull request (PR). This would allow our team to review the commits before a PR is opened, providing a more effective way to manage and correct any potential issues before they impact the main repository. This is an improvement that would significantly streamline our workflow and reduce the risk of errors.
1 vote -
Download multiple objects at once from a backup run
Given the related nature of many objects within a Salesforce Org. It would be helpful to be able to filter on and select records from multiple objects in a single data download.
1 vote -
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 -
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 long1 vote -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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
- Don't see your idea?