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.
81 results found
-
Support flow deletion at V44+
if the target flow is deactivated; and all prior versions are deleted, you can't delete the last remaining flow version in the target org. The error you get is "Insufficient access rights on cross-reference id".
Copado provides a solution (https://docs.copado.com/article/8l069zes9f-destructive-changes-in-copado-doesn-t-support-flow-and-process-builder) wherein the user can specify the contents of the destructive-changes.xml file (enumerating the versions to delete) but Gearset has no way to inject such a file into a compare/deploy (esp a CI deploy)
with SFDC pushing more and more dev into Lightning Flow, deletions are inevitable in many orgs as things get refactored/renamed
2 votesWe have added a problem analyzer that will detect when you are deleting a flow, and update the destructive changes xml to include all the versions automatically.
Thanks for the suggestion!
-
Add support for CMS Connect Sources
Please add support for CMS Connect Sources in the comparison filters as well as the deployments and CI jobs.
We're working with CMS Connect in our current developments of a customer community and we'd like to deploy this metadata as well.
See the metadata api documentation: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_cmsconnectsource.htm2 votesWe have now added support for the CMS Connect Source metadata type.
-
Introduce 'ListView' as an option in 'Metadata filter' tab
When navigating to the 'Metadata filter' tab to select filters, there are currently 122 options, however 'List View' is not one of them.
When navigating 'Metadata Types & Components' in Workbench, 'ListView' is described independently, and I have used it previously when deploying via ANT. Therefore I would imagine there is a way to identify List Views independently of 'Custom Objects'.
This would be a huge help with a Production monitoring job, as I do not mind if List Views are updated by certain users in Production, but currently they are flagged as differences. Basically, I want to ignore them…27 votesThis is now released, you will need to update the metadata filter for any jobs set up already to take effect.
You can now exclude list views as well as other subcomponents of custom object.
(Note: named items is not populated for subcomponent metadata types.) -
Unique filename of the generated report PDF
Currently, the name of the generated PDF file of the deployment report is always the same for a given source and target.
If we deploy from our "master" gitlab branch to our "production" environment, the name will always be the same.
We archive the report PDFs for documentation / compliance reasons, and we always have to manually rename the PDF file to make the name distinct.
It would be nice if the name of the report PDF was unique. This could be achieved by either including a timestamp or the deployment number into the filename.
1 vote -
Select more than one item at the same time
On "Items to include/exclude for Custom application" view, it would be really nice if we could select more than one item at the same time, using SHIFT shortcut.
When clicking on "Named Item", and if you want to select from the 49th line to 63th line for example, and to avoid to select manually 15 lines with 15 clicks.
We could just select the 49th line, and with SHIFT, click on the 63th line to select them.
Thx2 votesReleased on 10th of Aug 2022
-
configure which problem analyzer results to use in CI jobs
Being able to configure which problem analyser results to use in CI jobs.
For instance, we can’t deploy any changes to managed packages because the problem analyser will ignore them (even though we have components from a managed package that we can modify and deploy without issues), that would help to reduce our manual steps during deployments.
46 votesConfiguring which problem analyzers are run as part of a CI job can be done by creating problem analysis templates and applying them to your CI jobs.
For more information on configuring and applying these templates, please see the Gearset documentation here: https://docs.gearset.com/en/articles/4942022-problem-analyzer-templates
Regards,
The Gearset Team
-
Support the CustomHelpMenuSection metadata item
We use the CustomHelpMenuSection item to customise our Help & Training dropdown list in Salesforce, and we would like to include it in our deployments automatically.
It's been available in the Metadata API since version 45, but Gearset doesn't appear to support it yet.
Will it be available soon?
1 vote -
There should be an option to schedule unit test jobs weekly in Gearset
Hi Gearset,
I would suggest you to provide an extra option where we can select weekly ,daily or monthly schedule jobs in Unit Testing Jobs.Thank you,
2 votesYou can now choose which days of the week a unit test job should run, allowing you to schedule the job to run weekly.
-
Cloning package should copy over (prepopulate) description as well as friendly name.
I find myself having to go to the original deployed package to copy the description information or coming up with a new description for the cloned package. Would be nice to have this brought over from the original when cloning a package.
17 votes -
Keep the Deployment Friendly Name / Notes when you refresh a comparison
Keep the Deployment Friendly Name / Notes when you refresh a comparison
5 votes -
Ability to deploy remaining Omni-Channel Components
For Omni-Channel deployments, QueueRoutingConfig metadata type is now supported by Gearset. However, corresponding PresenceUserConfigUser and UserServicePresence metadata types are not yet available. This means a secondary Metadata API tool (e.g. ANT, Workbench) or other manual steps are needed to complete an Omni-Channel deployment.
Hoping all supported components for API deployment can be included in diffs for releasing all via Gearset.
5 votes -
Update the CI Jobs Page so you can organize, similar to Deployments History page.
We have a bunch of CI Jobs, and it gets a bit difficult to identify whose job is owned by who just by looking at it.
Maybe make it similar to the Deployment History tab where I can sort out things by clicking the options above like "Owner" or "Name" and it'll organize it the way the Deployment History tab you guys have in place.
2 votes -
GitHub Pull request
All user to submit pull request from within Gearset instead of having to jump out to GitHub.
3 votesWe’ve now added the ability to create a pull request for GitHub when the deployment has succeeded within Gearset.
You can read more about it from our blog post: https://gearset.com/blog/create-pull-request-in-gearset
-
Output information after CI Job regarding problem analyzer skipping some component deployment
I would like to get some information from the problem analyzer after a CI Job completes as it seems like if it detects a problem during the job it skips deploying some of the components, like user permissions.
5 votesYou can now see this under [View problem analysis fixes] for each CI job run.
-
Enable deployment of unmanaged packages and Lightning Bolt Solutions from one Salesforce Sandbox to Another.
Enable deployment of unmanaged packages and Lightning Bolt Solutions from one Salesforce Sandbox to Another.
1 vote -
add support for Live Agent and Einstein Chat Bot
We're using Live Agent and Einstein Chat bot but there is no way to deploy this in Gearset. Per Metadata API v43.0, these objects can be retrieved and deployed:
- Bot
- BotVersion
- EmbeddedServiceBranding
- EmbeddedServiceConfig
- EmbeddedServiceLiveAgent
- LiveAgentSettings
- LiveChatAgentConfig
- LiveChatButton
- LiveChatDeployment
- LiveChatSensitiveDataRule
since we use Gearset for all deploys to source and to orgs; omitting LiveAgent and chat bots means we don't have a consistent way of maintaining truth
2 votes -
Provide a desktop notification from browser when a validation or comparison is completed
It would great if browser notifications could be created/enabled to notify a user when a validation or comparison is complete when the user is off the the browser tab where the validation or compare is happening.
2 votes -
Allow us to configure a push notification when comparisons are done.
It would be great if we could configure a notification when a comparison completes. Sometimes comparisons take a long time!
7 votes -
Sort order of Orgs ignores friendly name
If you have friendly names for your org connections, the list of orgs presented on the Comparison page ignores these and instead sorts on sandbox name. Since the lines show friendly name left most; this is not natural to the human to see things out of order
Example
OrderFix (joe.blow@foo.com.story003)
Invoicing (joe.blow@foo.com.story010)
AlphaTest (joe.blow@foo.com.story091)when what the eye wants to see is:
AlphaTest (joe.blow@foo.com.story091)
Invoicing (joe.blow@foo.com.story010)
OrderFix (joe.blow@foo.com.story003)1 vote -
Active Link to Deployment Destination
When you finish a deployment you get a "Deployment Summary" screen that has handy details. It does not, however, have a link to the commit/branch in Github or other site where the destination ended up. I have to jump to my Github page and refresh instead of having a direct link. Yes, it's a tiny feature but is useful for a Gearset newbie like me.
1 vote
- Don't see your idea?