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.
1411 results found
-
Extend permission to enable ArchiveViewer connector for users
Enabling ArchiveViewer connector is limited to only the Archive Owner. Ownership can be transferred but maintaining Archive Owner is crucial to organization structure and should not be changed. However, the ability to enable ArchiveViewer connector for Archives should be extendable to other users as Archive Owners are usually Platform Owners/Management that does not perform deployment/development work.
1 vote -
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.
1 vote -
automagically refresh the list of salesforce connections when I add a new one.
When I am choosing a source or destination salesforce organization, I can add a new connection, but when I save it and return to the choice page the new connection isn't listed in the drop-down unless I refresh the page. Seems to me that you could trigger a background refresh on save so that the drop-down is auto-updated.
1 vote -
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 -
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 -
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.
1 vote -
Suggestion for Org Intelligence Enhancement
Add a dashboard within Org Intelligence that tracks metadata changes. Provide the ability to select a date range and view changes across key metadata types such as Objects, Fields, Validation Rules, Apex, Page Layouts, and more.
The dashboard should include interactive filtering functionality that allows users to drill down into individual metadata components. It should also allow customization of which metadata types are included and display rollups summarizing changes, deletions, and modifications, along with details on who made each change.
1 vote -
Deleted field references doesn't get auto-cleaned up in Layouts and ReportTypes
If a custom field is deleted, its references in Layouts and ReportTypes are not getting deleted in the environment branches. So each time, developer had to edit all the report types and layouts to remove the deleted field references. Imagine, this being done for hundreds of reportTypes in the system. If this cleanup is automated using Gearset, it would be more helpful for the developers.
13 votes -
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 -
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 -
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 -
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 -
Delete feature branch ONLY after production deployment
The ability to delete feature branches only after merging with master branch (which runs the ci job to deploy to Production). Currently the feature branch will delete if there is no PR attached with it. There are instances where I may want to delete a PR to the 'QA' or 'Release' branch but still want to keep the feature branch. Currently this is not possible.
6 votes -
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
- Don't see your idea?