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
-
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.
-
Be able to create a CI Job to auto-commit (changes between two orgs) to source control
We have both admins and developers working within our SFDC environments.
Admins typically deploy across environments, so being able to create a CI job to keep the repo updated with these org-to-org changes would be ideal.
12 votesIt is now possible to choose a source control system as the target of a CI job.
For source control best practices, have a look at our whitepaper: https://gearset.com/blog/whitepaper-guide-to-implementing-version-control-for-salesforce
-
Deploy detected changes to other orgs
Being able to detect and roll back changes to orgs through the change monitoring is cool, but what I'd really like is to deploy detected changes to other orgs.
For example, if we detect a new configuration change to Production, being able to clone that change back down into our Sandboxes directly from the monitoring snapshot would be a real time saver. Or if someone deleted something in Production, being able to make that destructive change down into the Sandbox.
It would help us remove the step of running the comparison and pushing the changes after seeing a monitoring job…
14 votesThis is now shipped and live in the app! We’ve written a small blog post that walks through the feature and the use case.
https://gearset.com/blog/migrating-quick-fixes-in-salesforce-to-source-control
-
Org metadata snapshots
Allow a snapshot/backup of an org prior to running a deployment. Allow us to use this as a source of a new deployment if we want to revert any changes previously deployed, or at least download the package.
10 votesThis feature is now available. You can take snapshots of your metadata on-demand via the Change Monitoring feature and download the zip file created.
Use the local files option when configuring your comparison.
-
Be able to add the friendly name when adding a new org
Be able to add the friendly name when adding a new org as this saves going back to the list of orgs and adding then
1 voteOnce you’ve authorized the org, a friendly name field will then become available in the dialog to allow you to also specify its name.
-
Ability to sort on the Change monitoring overview Page
From the Change monitoring overview page it would be helpful to sort by the various "Headings" currently they are not sortable at all.
1 vote -
Character count for "Deployment notes"
Add character count for "Deployment notes". Handy for example when integrating with Github and using its web UI, where the commit messages (deployment notes) get "truncated" past 72 chars I think.
1 vote -
Ability to Sort and Filter the Test Monitoring Overview Page
As a consultant it would be nice to be able to Sort/Filter on the Test Monitoring Overview Page as we have many Jobs setup already and expect to expand to many many more it would be helpful to be able to sort and maybe even filter this list.
1 voteHi Josh,
You can now filter and sort the test monitoring overview page.
Regards,
Stephen
-
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.
-
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.
-
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 -
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.
-
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 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 -
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 -
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
-
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 -
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
-
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
- Don't see your idea?