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.
348 results found
-
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 webhooks for VSTS (like BitBucket and GitHub)
You offer webhooks for BitBucket and GitHub source control branches (so you can build on-demand if the repository is updated). We use VSTS Git at our organization and this functionality would be really useful for us!
VSTS offers webhook functionality-- see here: https://www.visualstudio.com/en-us/docs/marketplace/integrate/service-hooks/services/webhooks
Please give it a chance!
1 vote -
Remember last used Custom Filter, or set a Default Filter
It would be nice to be able to set a default custom filter.
Since the default "Default comparison" filter doesn't suffice for me.15 votesGearset will now remember the last used comparison filter.
-
The filter does not allow you to drill down into the Custom Objects, we have approx 300 objects this takes considerable time to run for the
Filter on Custom Objects prior to running a comparison similar to Salesforce Change Set, select the required object and fields to compare
3 votesGearset now has support for advanced filtering, prior to kicking off the comparison.
You can select components within an individual metadata type and save that as a common filter for your team to use. You can read more on our blog: https://gearset.com/blog/fine-tune-your-org-comparisons-with-advanced-metadata-filters
Thanks for reporting and I hope you find this useful!
Kevin
-
GitLab for destination of comparaison
I can't compare my sandbox org as source against my git repo as destination of compare.
I can see : gitHub, bitBucket as destination but no Gitlab.
It would be nice I if I could choose Gitlab as well and update my repo from changes in my org.17 votesWith our latest release, you can now add connections to any git-based repository using a username/password connection. This means you can now use GitLab as the target of your comparisons and deployments. See how to set up these connections in this blog post: https://gearset.com/blog/deploy-metadata-to-any-git-repository
-
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 -
Improve formatting of the XML pushed to git
Is it possible to improve the formatting of the XML?
The XML returned from MavensMate is formatted better.It's mainly just missing new-lines.
2 votesWe’ve made a bunch of improvements to the XML formatting this year, including tidying up which namespaces are included and having more consistent indentation and newline behaviour.
As always, we love feedback on the changes we’re making so please submit another idea if there is still improvements we can make in this area!
Thanks,
Kevin -
Allow user to choose the folder in a git repo that contains metadata
Improve git access by allowing the user to define folder where metadata is stored in a git repo.
We are not keeping directly content of src in git branch but src folder because we have there also few other folders.
The problem is that if I try to compare sandbox with git then I am getting results that all files are new.
2 votesThat’s great!
I’m glad that the issue was resolved for you with the adjustment in the location of the package.xml.
Regards,
Stephen
-
Support auto-complete in the dropdown for Source Control repos
Would it be possible to provide an autocomplete dropdown when selecting the git-repo? Similar to selecting the Salesforce-org.
2 votes -
Be able to create a CI Job with the option to validate only (and quick deploy later).
For the case where users have committed changes to a "master" branch, it would be useful to automatically run a full validation on the new commit in the Production environment. In that way, a deployment manager can review the changes and quickly deploy a validated package that has passed all tests in Production.
7 votesHi Nghi,
We’ve added the ability to review and deploy a validation CI job.
Catherine
-
Ability to schedule deployment past "expiration date"
We sometimes want to schedule a deployment a week or more away. After validating a package, the app has all the information it needs to deploy it, regardless of whether or not the validation expired in SFDC.
1 vote -
Add button to go from validation package to comparison
Use-case is where we have validated a package, but not been able to deploy it before expiry. Eventually, we are able to deploy it...
At this point, I'd like to be able to go from my validation package in the history straight to a comparison with the same objects selected. Then, I'll be able to make sure everything still looks good and validate/deploy again.
1 vote -
Provide link to the deployment status
When CI Jobs are running or when monitoring a deployment, it would be nice to have a link to the target salesforce environment's deployment status page.
2 votesThis work has now been completed, so a link is shown on the `Deployment in progress…` page that will take you directly to the deployment status within the target Salesforce org.
Thanks,
Kevin -
Objects in deployment report did not deploy - Various Custom Translations
Hey guys -
I am experiencing an issue where i am selecting various custom translations to deploy and the deployment report states deployed, but they are coming up in a new compare and have not been deployed in reality.
These custom translations are recommended to be removed from the deployment in the fixes / recommendations screen. However, i deselect the objects in order to deploy them. Then both validation and deployment succeeds w/ said objects in the deployment report.
Maybe it's something i am doing wrong? I could get on a call to discuss my scenario and run through it…
1 vote -
Remember my default source control system and default to it
We use Bitbucket not git hub. So on compare metadata screen when I go to Source Control radio would be nice for the version system to default to bitbucket.
Small tweak I know but annoying to change every time. Easiest might be that the drop down list stays set to whatever system you used last?
3 votesHi Douglas,
I’m marking this as completed because this feature is already implemented and should remember the last VCS system you used – if it isn’t working then that’s a bug!
Note that it’s currently only implemented on the Compare and Deploy page, and is specific to the source/target (so using Bitbucket on the source side won’t carry over to the target side until you’ve used Bitbucket once on that side, and vice versa).
The preference is only saved when you actually kick off a comparison. Clearing your local storage for `app.gearset.com` may clear up any issues if you’re having problems.
We’d love your feedback if this isn’t working or isn’t implemented as you’d expect it to be.
Thanks,
Oli -
View deployed components from a CI Job
Display components deployed via a CI Job. In my case, there are a greater number of total objects deployed than I would have expected; but, I have no way of viewing the comparison for what is automatically being deployed.
6 votesGearset now supports viewing the underlying comparison that ran as part of your CI job.
Press the `View comparison` button beside a particular entry in the CI history to see the components
-
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
-
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 -
Prev/Next buttons did not function for setting the focus when in APEX view mode
When viewing an Apex class with differences, the Prev/Next buttons did not function for setting the focus in APEX view mode however they did function when in XML view mode.
2 votesWe’ve identified and fixed the issue. Thanks for reporting it.
-
Under deployments in the validated tab there is no column for the name of the deployment. Please carry over the friendly name.
When a draft is validate, as the gatekeeper for production I cannot see what a coworkers validated deployment is about. It seems like the friendly name should carry over as a column to display on the validated tab, also into the deployment history.
10 votesThis is now implemented and released. As on the deployment history page, you can now name your validated packages.
This name will follow over from a draft deployment and to the deployment history.
Thanks for the feature suggestion!
Oli
- Don't see your idea?