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.
1468 results found
-
Body: When a Config Data / CPQ deployment fails or partially succeeds, there's currently no way to export the list of failed records and the
Body:
When a Config Data / CPQ deployment fails or partially succeeds, there's currently no way to export the list of failed records and their error messages. You can only review them on screen.For Metadata deployments this already works well — from Deployment history you open the deployment, click "View errors", and an export option is available there.
Please add the same export capability to the Config Data errors page. With larger data deployments, the number of failed records can be significant, and having the full error list in a file would make it much easier to triage the…
2 votes -
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 -
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 -
Comparison API
I would like to have a Comparison API. An API that would allow me to:
- initiate a Comparison between two saved sources
- specify filters
- retrieve a list of comparisons
- retrieve status
- download the results of a comparison
- send a list of metadata items along with a comparison ID in order to select those items for deployment
- trigger a merge/deployment1 vote -
Don't ruin my day when a flow activation fails - Add Flow Activation Fails in Summary
The summary only shows the flows that were successfully activated. It doesn’t surface activation failures for individual flows.
So the behavior you saw can happen:
The deployment completes successfully
Gearset attempts to activate all flows after deployment
The summary lists only the flows that activated
Any flow that didn’t activate won’t appear as a failure in that summary
That’s why it can look like a “clean” deployment even if one flow stayed inactive.1 vote -
View line-by-line code coverage in Pipelines
Automated unit testing has the ability to view line-by-line code coverage, but tests run by a CI job in Pipelines does not. This would be very valuable, especially when test coverage is below the required threshold to see where the issues are in the next environment. This information is available from CLI but it would be much better to have it surfaced in Gearset on the PR.
1 vote -
Centralized Activity & Audit Log for Gearset Actions
It would be valuable to have a centralized, searchable audit log showing the activities and actions performed within Gearset.
For example, this could capture events such as validations, deployments, branch/PR creation or deletion, configuration changes, and other user- or automation-initiated actions, including who performed the action, when it occurred, and the relevant project/environment.
This would provide much stronger auditability, traceability, and operational visibility, particularly for teams using Gearset as part of regulated or controlled deployment processes.
As a related improvement, it would also be useful for Gearset's Jira integration to optionally post comments when Git branches or PRs are deleted,…
1 vote -
Notification when a data backup is edited, disabled, or deleted.
We need to receive a notification when a data backup job is edited, disabled, or deleted. To ensure we always have a prod data backup job running.
1 vote -
Azure DevOps - Status visible in the "Azure work items" tab.
Azure DevOps - Status visible in the "Azure work items" tab.
1 vote -
"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 -
Allow us to see which components belonged to each individual feature when we create releases.
When we create a release, you have to go through some clicks to ultimately find which features are in it. That is great and needed.
HOWEVER, it would also be super beneficial for us to be able to see which components were in each individual feature, so we can look back to the jira stories faster to identify what the changes were, as that holds all the solution notes and in depth details of component changes.
1 vote -
Restrict the branch from the promotion if developer add any metadata type other then the metadata types on CI Job filter.
Currently Gearset is giving a warning on PR if metadata type added on the branch doesn't present in CI Job filter, instead if we a have something to restrict /block promotion it helps.
Scenario: Even if developer uses CI Job filter at time of comparison still, they will be able to compare additional metadata types, hence they commit those to the branch. At the PR level it is showing as warning message which developers are missing and promoting changes. After promoting they are coming back and asking why those haven't deployed even it is showing as deployment successful.
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 -
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 -
Feature Request: Bulk / Mass-Selection for Filtered and Sorted Objects in Backup Settings
Problem & Pain Point
Configuring data backup jobs for large orgs is currently a highly manual and time-consuming process.While the Recommended objects filter is a helpful starting point, it unfortunately includes many objects that we do not care to back up, leading to unnecessary noise and storage bloat. To circumvent this, our goal is to only select objects that actually contain records.
While Gearset allows us to sort the table by the Records column to bring populated objects to the top, there is no way to mass-select them. Having to manually click hundreds of checkboxes one by one is…
1 vote -
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 -
assignment writing services in UK
University assignments can quickly become overwhelming when multiple deadlines overlap. If you're considering assignment writing services, it's worth looking for a provider that values quality, originality, and clear communication. Reading authentic reviews and comparing different options can help you make a more informed decision https://masterassignmentwriter.com/assignment-writing/
1 vote -
Allow pre- and post-deployment steps for items that cannot be deployed through the Metadata API
We encounter a variety of user stories that require manual changes to items that cannot be deployed through the Metadata API. If these are the only changes required, there is no way to track these pre- and post-deployment steps, since a PR (and thus a metadata commit) is required to add the steps in Gearset.
2 votes -
flow renamed element
When comparing Flows, we might be updating (API) names of Elements, according to our naming conventions.
Gearset then treats them as new on the source, and deleted on the right without linking them.It would be great if this can be improved, either automatic, or giving us the option to provide both API Names, so then the comparison can be rerun.
1 vote
- Don't see your idea?