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.
357 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.
10 votes -
Support a .gearsetignore file to exclude non-metadata paths from CI triggers
Salesforce DX repositories hold more than deployable metadata: AI agent guidelines, documentation, package.json, .prettierrc, lint configs, scripts and so on. A push that only touches these files still starts a CI job. The job deploys or validates zero components, and on a production pipeline it can still run the full test suite, which can take an hour or more.
Gearset has no way to exclude paths from this. .gitignore isn’t a fix because it stops the files from being tracked at all, and we need them in version control.
Proposal
A .gearsetignore file in the repository root, with the same…3 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 -
Enable getting updates to developer environments from an integration branch rather than only from our base branch (main)
We'd like a pipeline setting option to specify a branch that updates to developer sandboxes come from, rather than being locked into using our base branch, which is main. We often have features sitting in our integration branch for up to a month before they work there way to main/production. Sometimes we take on new stories that have dependencies on another story that is not yet in main, but only in our integration branch/environment. We'd like to be able to specify a branch that updates to developer sandboxes come from so that we can use our integration branch instead of…
2 votes -
Expose all Gearset operations through APIs
Gearset can only be configured by a human through the UI. This leads to long, manual, and error prone setups with no way to create reproducible automation for common scenarios. We'd greatly benefit from having the ability to automate these setups through APIs or some Infrastructure as Code framework. Here are some examples of operations I'd love to automate or integrate into other workflows: initiate CI job PR validations, clear existing Updates from a developer sandbox, manage org connections, manage developer sandboxes in a pipeline, manage user permissions, manage monitoring jobs, manage unit testing jobs, mark manual steps as completed,…
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 -
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 -
Audible/Visual Notification when Cam is ready
The ask: an audible 'pop' sound (like the Support chat reply 'pop' or a push notification to my desktop) when Cam is done processing
There are many times when I fire up a conversation in Org Intelligence or Agent and navigate away while I wait for it to cook. This would help me get back to focusing on the project, while still feeling okay to jump over to answer a quick email/Slack while I wait.
1 vote -
Org Intelligence Scroll
This is so silly, but when I went to Org Intelligence, I scrolled down on the page itself and could not figure out where the rest of my orgs were listed. Turns out you have to scroll within the list of orgs... I feel like a slight change in the UI to show a mini-scrollbar or something would've helped me here. Thank you! :)
1 vote -
Support reusable metadata filters for Monitoring jobs
Gearset provides the ability to reuse metadata filters across CI jobs which allows you to configure it once and have the changes apply to all jobs referencing it. https://docs.gearset.com/en/articles/618760-manage-custom-filters-in-ci-jobs
The same functionality is missing for Monitoring jobs. It would be very helpful if Gearset adds this feature for all existing and future locations where metadata filters are configured for a job.
1 vote -
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 -
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
- Don't see your idea?