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.
1409 results found
-
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 -
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 -
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 -
Compare UI feedback after large salesforce project
- 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.
- 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 -
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…
3 votes -
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 -
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 -
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…
1 vote -
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.
- I want to deploy from my phone.
- I want to monitor PRs from my phone.
- I want to browse my Scheduled Jobs and Monitoring Jobs.
2 votes -
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 -
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 sandboxesSuggested solution:
- Allow multiple team members to be selected via the "Assign sandbox to team member" function.5 votes -
The Importance of Data Analytics in US Logistics Solutions
Data analytics has become a critical driver of efficiency in US logistics solutions. By analyzing real-time data, logistics companies can optimize routes, reduce fuel costs, and improve delivery timelines. Predictive analytics helps businesses forecast demand, manage inventory levels, and avoid costly delays or stock shortages. It also enhances transparency, allowing companies to track shipments accurately and make informed decisions quickly. In warehousing operations, data insights improve space utilization, labor planning, and compliance monitoring, especially in specialized areas like food grade product warehousing. Overall, data analytics empowers logistics providers to increase reliability, cut operational costs, and deliver better customer experiences…
1 vote -
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 -
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
exactly1 vote -
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…
3 votes -
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 -
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.
1 vote -
“Disable rules and automations” another use
“Disable rules and automations” functionality in Data Deployments – it’s incredibly helpful.
Would it be possible to provide this as a standalone feature, not tied specifically to data deployments? Ideally, it would:
Allow users to review the rules and automations on a given object
Deactivate selected rules/automations before a test
Allow user Reactivate them automatically once their testing is complete
Use case: This would be extremely useful for supporting testing scenarios. For example, when creating cases to test a new flow in debug mode, temporarily disabling certain rules and automations would simplify setup and reduce interference.
1 vote -
add record id as column to search results, or search with record ID from source org
Please check recent conversation thread with Sam. With my account nazrul.amin@lloydslistintelligence.com.nazrul
Another tip, would be great to search with Record Id's, as sometimes in orgs we have very similarly named products. Would make like easier finding the specific record you were working on
Nazrul • 6m
Or is it possible to expose the record ID as another column in the comparison results please?1 vote -
Add Webhook Error Logging and History for Outgoing Webhooks
When configuring outgoing webhooks (e.g., to GitHub Actions or Slack), errors and failures are not surfaced to the user, making troubleshooting difficult and time-consuming. Currently, after a webhook is triggered (or fails to trigger), there is very limited visibility into what payload was sent, what response was received, or whether an error occurred. If a webhook fails silently or returns an error, I have no way to view detailed logs or the history of webhook attempts. Furthermore, error messages (if any) seem to clear out whenever CI job settings are saved, and there is no persistent record of webhook activity.…
2 votes
- Don't see your idea?