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.
334 results found
-
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 -
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 -
Add spell checker to CI/CD pipeline
Spell checker helps maintain a high standard of accuracy, ensuring your content is reviewed in initial PR's itself. Just like how we use Clayton code feedback.
If typos is in customer facing texts in UI (which is can be a big problem in public facing application where large no of users visits.)
It would be good if spell checker can be added as a policy inside Clayton. So that we can find and fix issues easily.
Advantages
* We can also prevent potential PROD P1 errors.
* Enhanced Code Quality
* Improved Deployment Efficiency
* Reduced Technical Debt11 votes -
Add ability to validate commit messages for deployments
We require commit messages for deployments, but we actually need to go beyond this and validate the commit message format, checking for things like tagging ticket numbers in commit messages, formatting, etc.
If the commit message validation fails, deployment should not be allowed.
Some source control providers (e.g. GitHub) allow server-side pre-receive Git hooks which can perform such commit message validation; however, Bitbucket Cloud does not currently support this and it is unrealistic for us to switch source control at this point in time. Without this feature in Gearset we are unable to enforce formatting requirements on commit messages coming…
6 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.
18 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!
9 votes -
API to Manage CI Jobs
I would like an API to manage CI Jobs and Sandbox connections.
In our current workflow, we create new sandboxes and branches for large initiatives. Along with these, we need to connect the SB in Gearset, build the CI job, run it for the first time, and then tear it down when we're done.
We would like to be able to automate some of this.
- I have a branch and a sandbox
- I want to connect that sandbox in Gearset (would be great to do this programatically via api)
- create a CI job via api
- be able to run the…
4 votes -
View Deployment Summary from Pipelines
My team develops in siloed dev orgs. Once a feature is complete, we create a PR against an integration environment.
This triggers a test suite run in the target org and a peer code review. This process works well for Apex. However, admins on our team build automations in Flow, which are nearly impossible to review in GitHub due to the complexity of the XML.
To address this, we’ve been using Gearset’s Flow Navigator for Flow code reviews. Previously, it only took a couple of clicks to reach the Deployment Summary screen, and the Flow visualization made reviews much easier.
…
6 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.
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 -
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…5 votes -
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 -
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 -
“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 -
In Org Intel
Create a project-based workflow within Org Intelligence specifically for users who deploy via metadata deployments. Users can create a project, give it a name, add a description, and link it to related Jira issues. Admins, deployment managers, and other contributors can then add components to the project as part of the build, with the ability to leave comments on each individual component to capture context, decisions, and dependencies. The team can collaborate in one central place instead of using spreadsheets, reducing overlap and preventing missed items. Once the project is ready, a single click should trigger the comparison process via…
1 vote -
Reward Systems That Reinforce Effort
When it comes to helping students stay focused and consistent, reward systems that reinforce effort can make a huge difference. Instead of only celebrating perfect scores, these systems highlight progress, persistence, and improvement. Whether it’s earning points for completing tasks, unlocking small incentives for consistent study habits, or receiving badges for personal milestones, effort-based rewards encourage learners to keep trying even when challenges arise. This approach supports healthier academic mindsets and boosts confidence over time. Many educators also integrate reflection activities to help students understand why their effort matters. By aligning rewards with growth rather than perfection, teachers can naturally…
1 vote -
1 vote
-
filter back propagation
Add an open pull requests filter for back-propagation PR's.
1 vote -
Provide a visual indicator on upstream systems when out of sync with master
Often times we see drift items added to PR's in our upstream systems. It would be nice to have an indicator that shows if a static branch is out of sync with master.
3 votes
- Don't see your idea?