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.
352 results found
-
Auto-delete stale and abandoned branches
It would be great to have an option to automatically delete branches (and their PRs, if there are any) that have had no activity for a configurable period, e.g., 3 months. This would help teams be more organized and efficient by reducing clutter. Currently, branches are deleted only when their PR reaches main or when both the PR and the branch are manually deleted. Stale or abandoned branches that never get promoted sit there and create a mess, and cleaning them up means manually checking for open PRs before deleting them in Git.
9 votes -
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.
17 votes -
Allow us to mark deployment failures on the pipeline as fixed without the need for a new deployment
When there was an error on deployment and we fixed it, by doing a compare and deploy. We would like to mark the Error as fixed. So other users can see that the error already has been solved.
2 votes -
Notify When Metadata Is Not Enabled for Deployment
It would be helpful to have a warning/notification when metadata is added to a branch through a comparison but is not enabled for deployment.
We recently ran into a situation where the comparison allowed us to select managed package components and add them to the branch. However, the related metadata was not enabled for deployment, so those components were present in the branch but were not actually deployed to the target org.
It would be useful to have this notification either:
During comparison, when selecting metadata that is not enabled for deployment, or
When promoting the PR, if the PR…2 votes -
Support for decomposed permission sets
Please add support for decomposed permission sets: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_decomposed_md_types.htm. Permission set decomposition makes large permission sets much more manageable. Decomposed permission sets currently fail to deploy through Gearset. I confirmed with Gearset support that it isn't currently supported.
5 votes -
allow a second sandbox to pull PR changes before PR is promoted to main
Currently I have to manually apply a PR from another developer to my sandbox. It would be great if we could sync back a PR before it reached main or sync across from one sandbox to another
2 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.
7 votes -
Add The Projects Feature to Modular Pipelines
It would be immensely helpful for my team if gearset implemented the projects feature in normal pipelines into modular pipelines. Testing takes different amount of time and this happens across regions.
1 vote -
Track Custom Metadata Types in the Gearset extension.
I'd love to see Setup>Custom Metadata Types tracked. Both the Custom Metadata Types themselves and the records within them.
1 vote -
Quick Fetch Latest Changes
The quick fetch feature would just ensure that the components that already exist in that feature branch, are refreshed i.e. their latest version is fetched and automatically added to the commit with the click of a button, without having to go into the comparison view again, from which, now the user can create a new pull request.
2 votes -
Pay as you go Pricing
There has to be a pay as you go pricing model for Contractors who have random uptime and downtime in using Gearset.
2 votes -
"Org intelligence" should support "org change history"
I would like to be able to utilize org change history inside org intelligence. Currently, AI cannot answer questions based on changes captured through jobs.
1 vote -
Multiple announcements in pipeline
Currently we are unable to add more than 1 announcement in the pipeline. If I want to make more than 1 announcement in pipeline that would help me and my team a lot. Requesting a new feature which allows us to add more than 1 announcement in the pipeline
1 vote -
Upload a screen shot of the Flow Application error and get details on how to fix it
I saw a demo from Copado today where they are able to upload a screen shot of the Flow Application email into their AI agent and it spit out details on how to fix the error in the flow. Is this something Gearset offers or plans to offer in the future?
2 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 Debt12 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…
8 votes -
Org Intelligence Feature Request
Import impact analysis from Org Intelligence directly into Azure Boards, Jira etc. Copy paste doesn't work due to format issues.
For example, I asked impact of updating a trigger to gearset agent, it did return impact analysis in detail but I would like this information to be sent to Azure notes or some other field so that BA's, Dev's and everyone within the team has access and can see what they are dealing with and be aware of what to test for a particular update/change.
1 vote -
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 -
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
- Don't see your idea?