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.
1444 results found
-
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 -
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 -
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 -
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 -
Option to Export Full Comparison (Including JSON Metadata Differences)
Currently, when exporting a comparison from Gearset, the CSV includes a list of all items from the comparison. However, the export does not include the JSON data that represents the metadata differences between environments.
It would be extremely useful to have the option to export the full comparison, including the detailed JSON metadata diff.
Use case:
Our team is exploring ways to automatically generate changelogs whenever we make deployments. Being able to export the JSON comparison data would allow us to feed that information into an AI agent to generate a structured, human-readable changelog.Proposed enhancement:
Add an option to…
6 votes -
Automatically create a ServiceNow change request when a release has been created
We use ServiceNow for a change management processes. All changes to a production system require a change request. We release changes to production multiple times a week and even multiple times a day so this manual creation of ServiceNow change requests becomes tedious. It would be great is gearset could provide a way to automatically create a ServiceNow change request and auto-populate the description in servicenow with a list of changes included in the gearset release. It could be taken further like default assignment groups etc, but just creating a change request with the gearset changes and leaving it in…
2 votes -
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…
7 votes -
Darkmode option
It would be really helpful having a dark mode of gearset UI. A big number of devs prefer dark mode over bright mode. Since gearset is a tool mainly used by devs, would be good to give to devs the option to customize their UI.
20 votes -
Migrate a user to different login method without new acount or allow same user with multiple login methods
For each login method a user gets assigned a new account and has to re-setup all of their person connections. Please allow an Enterprise Gearset Admin (Owner) to update or migrate a user from one login method to another. Or allow the user to authenticate using any of the allowed methods without creating a new user account.
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?
1 vote -
From the gearset pipeline view, i wish there an option to export all the pull-requests including the respective git branches in a csv or .xl
From the gearset pipeline view, i wish there an option to export all the pull-requests including the respective git branches in a csv or .xlsx format
1 vote
- Don't see your idea?