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.
1485 results found
-
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
Add AWS Bedrock Integration for AI-Powered Deployment Reviews and Release Automation
As more teams adopt generative AI in their DevOps workflows, it would be valuable for Gearset to offer an AWS Bedrock integration.
Potential use cases include:
Generate AI-assisted deployment summaries before promoting changes.
Review metadata differences and highlight potential deployment risks.
Explain deployment failures with actionable recommendations.
Produce release notes automatically from deployment changes.
Help identify dependency or configuration issues before deployment.
Support organization-approved foundation models through Amazon Bedrock to meet security and compliance requirements.Many enterprises already use AWS services, so an AWS Bedrock integration would allow them to add AI capabilities without relying on external AI providers. It…
1 vote
- Don't see your idea?