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.
10 results found
-
Prevent Deployments from Including LiveChatButton with Omni-Channel Routing
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_livechatbutton.htm
LiveChatButton metadata that is routed using OmniChannel is not supported with the Metadata API and the deployment will fail.
It would be great if Gearset had an analyzer to remove this for end-users to prevent the error.
The following property is null for LiveChatButtons routed through Omni-Channel
<routingType xsi:nil="true" />
1 voteWe have now released the problem analyser requested – thanks for the suggestion.
-
New Analyzer to prevent endpointURL changes for Outbound Messages in Sandboxes
A major pain point and blocker to use automated CI jobs is that we cannot include workflow rules because we have outbound messages set up to specific test endpoints per sandbox/environment. As the workflow metadata type allows us no ability to filter by workflow rule name (it's by object), this means we have no option but to manually run the comparison and deployments for each of our sandboxes.
It'd be great to add a problem analyzer to suggest not changing the endpointURL field on outbound messages when the target is a Sandbox. This way, you can deselect it manually when…
3 votes -
Remove botUser from Einstein Bot metadata
The metadata for EInstein Bots includes a tag called "botUser" that contains the username of the user you've specified to run the bot as. Because it contains a username, the deployment fails unless you have the exact same username in both environments.
My current workaround is to deactivate the bot, remove the running user (which removes the botUser tag), deploy, then reset the changes that I made.
Can we get a problem analyser that will detect and remove this botUser tag so that the deployment will complete?
1 voteHi. We have implemented a PA for this now, which will remove the BotUser field if needed to prevent Gearset from trying to overwrite the user with one from the source.
-
Upgrade to PMD 6.17.0
Current version is 6.11.0.
We should be consistent with newer version. We are having issues with older version in Gearset regarding the ApexDoc rule.
The issue was described and discussed with Valerio in the chat.
Thanks
7 votesWe upgraded to 6.21.0 today. Thanks for the suggestion.
-
Add an option to disable the "repository sanitizer"
The "repository sanitizer" performs unsolicited/silently changes which confuse users and generate issues. For instance, if you have Apex class permissions in profiles for classes which are part of a managed package and are not present in the repository, this sanitizer will modify the permissions to false which is obviously a disaster, (and the changes can happen any moment, while users are trying to deploy something completely unrelated hence the confusion).
We know the solution is to have the classes also in the repository but for managed packages that's unnecessary extra work since then we need to be updating them every…
12 votes -
Be able to sort/filter Validation Failures during Deployments
Like how it used to be, when I could see all the Validation Failures on one screen. I'd just Snipping Tool them, head Back to Results and fix them, quick and easy. Now the Failures are scattered within the Successes with no way to filter or sort them.
1 vote -
Export PMD rulesets/configuration as xml file
This would allow us to configure our rules in Gearset and then apply the same ruleset during our local development. Until we can upload our own xml config file, please add the ability to export the Gearset rules instead.
see related idea: https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/34668196-allow-pmd-to-be-configured-by-uploading-a-xml-file
2 votesYou can now export the pmd rules as xml by going to the static code analysis rules page:
https://app.gearset.com/static-code-analysis-rule-sets -
Upgrade to PMD 6
PMD 6 includes useful stuff like allowing annotations in the code to suppress warnings. It would be great to be on that version.
Stephen told me via the support chat that it wasn't simple to just upgrade, so I thought I would submit it as a feature request.
2 votesHi Aidan,
We’ve now upgraded to PMD 6.3 which includes support for suppressing warnings.
Regards,
Stephen
-
Warn when deploying objects without profile settings
I build a VF page, test it, deploy it and discover much later that I forgot to add profiles other than system admin to the page. Users can't see the page and get a permissions denied error.
So, the suggestion is to have a an optional analyzers that warns when deploying a new VF page to a target org where the only permission is System Admin. While this could be legit in some use cases, in most use cases, this is a self-inflicted omission.
2 votes -
CI deployment failure details in webhooks
Webhooks for CI deployment failures simply say "Deployment failed with (179/180 components deployed)" instead of describing the failure in more detail, including the Object and Error Message
6 votesDue to the potential number of items that could be listed we have restricted the number displayed to 12 since there could be hundreds, and provided a direct link to the errors page for convenience so it’s easy to view the full list of errors should there be more.
For the subset displayed, we’ve added:
- Item name
- Type
- Reason for error
- Don't see your idea?