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.
1469 results found
-
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 -
When we have the problem analyzer suggest to remove things (like fields) an option to also add that field would be great
Having the ability to add a field instead of just remove it et al in the problem analyzer would be sweet
1 vote -
Add into Problem Analyser InstalledPackage that will default to AllUsers
Currently, Gearset’s Problem Analyzer correctly identifies issues with InstalledPackages, such as suggesting activateRSS be set to false to avoid deployment failures. However, it does not yet account for the securityType field.
When an InstalledPackage is deployed without a defined <securityType>, Salesforce defaults the access level to AllUsers. In a production environment, this is a significant security risk, as managed package components and data access should typically be restricted during the initial deployment.
I am proposing an additional check within the Problem Analyzer for InstalledPackage metadata:
Detection: Identify any InstalledPackage in the deployment package that is missing the <securityType> tag.
Recommendation:…
3 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 -
allow CI jobs to run Apex tests regardless of which metadata changed
When a CI job has Apex unit test behavior configured to run specific test classes or a test suite, these tests will only execute if the deployment contains any Apex changes. I would like to execute certain Apex tests every time my CI job runs so I can be confident that my changes haven't caused any unintended behavior.
I'm building a feature and have maintained an Apex test suite which covers all of the Apex which supports that feature. I would like this suite to execute for every CI job run, regardless of whether any Apex code is changing, to…
1 vote -
Ideas for improving the automated testing feature
I have a few small ideas that I’d like to share:
- It would be useful to support wait times in minutes, not only in seconds.
- After the last step, it is currently possible to add a wait or another action, but only via the dropdown menu. It would be helpful if a plus button was also shown after the final step, consistent with the other steps.
- It would be useful to have additional date variables for Last Month and Next Month.
- It would be useful to have an auto-incrementing integer variable, where the value increases by 1 each time it…
1 vote -
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
- Don't see your idea?