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.
1451 results found
-
Auto-delete feature branches only after final deployment. Current deletion can hinder troubleshooting if pipeline promotion fails.
The current "Auto delete feature branches when there are no PRs open against the branch" setting works well for general cleanup. However, in pipeline-driven deployments, a branch can be deleted even if the change fails to progress to the next stage.
Consider adding an option to delete feature branches only after the deployment successfully reaches the final environment (e.g., Production). This would preserve troubleshooting visibility when pipeline promotion fails and help teams investigate root causes before the branch is removed.
5 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.
14 votes -
Automatically detect drift between the org and main git branch
Currently we can automatically monitor and report on changes made to an org via the Change Monitoring dashboard. This compares an org snapshot to the previous days snapshot.
However, what would be really useful now we have pipelines enabled is the ability to automatically report on org drift from our Github main branch, using a specified filter (i.e. the same filter as our Pipeline CI Jobs use). This would allow us to track, understand and hopefully reduce the amount of drift that occurs in pipeline-relevant objects, making the pipeline more robust.
18 votes -
Commit test class selection
When initially creating a commit, the only way to specify tests is to manually create a comma or new line separated list. If the validation fails, there is then an option to add tests with a nice searchable/selectable list before revalidating. Can this test class selection UI be added to the initial commit process?
3 votes -
Validate configdata deployments
We are implementing RCA and storing the configdata in source control. Because it is a data deployment and not a metadata deployment, no validations run to ensure the data will deploy correctly. It would be great if there was some way to run validation for the data deployment before merging a pull request that merges it to the org as a check similar to metadata validation.
3 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.
6 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.
4 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.
1 vote -
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 -
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.
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 -
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 -
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.
1 vote -
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 Debt11 votes -
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 -
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 -
Ability for custom masking on Email fields
Would love to be able to customize masking on email fields. When I currently mask an email field Gearset will make it something like 3d50b95f686844c6@gearset.invalid and I have no control over customization. I want to retain what the original email was so users can fix it and sent to it, if needed. I just want the email “broken” so it’s not used accidently through automation. Being able to customize the obfuscation would be very useful.
6 votes
- Don't see your idea?