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
-
Multi-Select Filter on Deployment History Page
It would be nice if the drop-down filter on the deployment history page allowed multi-select. My use case is filtering all successful deployments to production. Seems like it only supports one or the other now.
2 votesWe’ve now added more advanced filtering to the deployment history page to enable multi-selection. You can find the filter menu via the dropdown next to the text search box.
-
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 -
Add support for the CspTrustedSite metadata type
It would be nice if Gearset could add support for the CspTrustedSite metadata type (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_csptrustedsite.htm) to its supported metadata list.
1 vote -
Add support for the PlatformCachePartition metadata type
The Salesforce metadata Api supports the PlatformCachePartition metadata type (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_platformcachepartition.htm), but it's not currently available for comparison and deployment in Gearset.
Can you add it to the supported metadata types list in Gearset?
2 votes -
Add a "Clone Package" to the Validate packages tab
Allow users to clone a validated package just like that can clone a deployed package.
3 votesWe’ve now added a dedicated Clone Package action to the validated packages table for Enterprise users.
-
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 -
When creating a scratch org, allow a user to define the expiration number of days
Currently, when creating scratch orgs, the system automatically sets the expiration to seven days. However, scratch orgs can last as long as 30 days. Would it be possible to define the expiration number of days during creation?
2 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 -
Add a "Clone package" button to the Deployment Results page
My workflow is currently to deploy a change, browse to the deployment history to find my deployment, and immediately clone the deployment for another environment. It would be really nice if the clone button were available upon a successful deployment.
5 votes -
Ability to Clone Button on the Draft Deployment page
Can you create a Clone Button on the Draft Deployment page similar to the Clone Button on the Deployment History page? Some times we collaborate on a deployment and one user will take over. We want to be able to deploy the package as the current user, not the original one that made the draft.
10 votesThe ability to clone draft deployments is now available on the enterprise tier.
-
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 -
Preview Deployment Details in Deployment History
On the Deployment History page, it would be nice to have a little popup window to view some of the files from the Deployment Details instead of having to download the Deployment Report
7 votes -
Run Tests During CI Jobs
There are some similar but not exact posts below so I'm writing about a new one. We would like to be able to specify an option to run tests when deploying via a CI job from git (Bitbucket) in our release sandbox. If any of the specified tests fail, the CI job would fail and the deployment rolled back. It would be great is we could specify whether to roll it back or not when configuring the job but if that is too much too bite off, just failing the job would be helpful. Thanks!
3 votesIf you edit your CI job then you’ll have four options:
1. Default test behaviour
2. Don’t run any tests
3. Run only your tests
4. Run specific testsYou can select the test level that you’d like for your CI job and it will be respected and pass/fail your CI job accordingly.
Thanks for reporting and I hope this helps!
Kevin
-
Support Wave Analytics Metadata
We have been engaging in quite a few Salesforce Analytics (ie. Wave Analytics, Einstein Analytics or whatever the current branding label) projects lately. Version control on all of the related metadata is critical it would be enormously beneficial for Gearset to be able to support these metadata elements.
The following Analytics metadata types are supported in the Metadata API:
WaveApplication
WaveDashboard
WaveDataflow
WaveDataset
WaveLens
WaveXmd
WaveTemplateBundlePlease consider adding this to the roadmap for immediate consideration!
Best regards,
Mike1 voteThis has been shipped and we’ve written up an overview of the feature: https://gearset.com/blog/gearset-and-einstein-analytics-deploy-wave-applications-with-ease
-
Add Lead conversion support
Please add support for the LeadConvertSettings metadata.
See https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_leadconvertsettings.htm for details3 votes -
create branch
It would be nice to be able to check Salesforce changes into a new branch in Github (or other git repos). This would provide admins an easy entry point for their changes into a git repo without having to learn the esoteric git command structure.
2 votes -
Run external tools like PMD as part of Schedule Tests/Monitor Org
PMD tool that does apex code 'quality' measurements would be kind of cool to run (optionally) as part of a regular monitoring/test job. This could be generalized to any external tool
1 voteGearset will now run PMD to track code analysis as part of the Monitoring and Backup flow. The plan is to roll this out to other parts of the app so we can more easily track the change in code quality.
-
A way to view failed deployments from Gearset
Right now if a deployment fails in Gearset, it doesn't show up anywhere within Gearset; it just sends you an email. It would be nice to have a place to view failed deployments and retry them (maybe it only failed because the environment was locked), just like you can with successful deployments in Deployment History.
3 votesGearset now shows failed deployments on the deployment history page: https://app.gearset.com/deployments/deployed
-
Be able to require a commit message for deployments
Sometimes a user may forget to add in a commit message before deploying, so the history in our source control is "no commit message" which is not editable. Can we add a feature to be able to turn on marking commit messages as a requirement for deploy?
10 votesThis has now been shipped.
The team owner can now enable deployment notes to be required via the setting located in the account summary page.
-
Ability to pause CI jobs
Ability to pause a CI job. This would allow the CI system to keep our sub environments (stage, dev, beta) updated all the time, but when we want to develop on one of them we could then pause the CI job so our changes don't get deleted. Then once we have deployed the changes to prod we can reactivate the CI job to keep things in sync.
5 votes
- Don't see your idea?