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.
337 results found
-
Remind me what I just validated
I am working on 10 things at the same time like usual. I started a validation about an hour ago. I open the tab where the validation was occurring and it says it succeeded. Yippie! Problem is I don't remember what I was validating and nothing on the success screen tells me which system I was validating against. I want to be sure I am going to deploy the right thing to the right server at the right time.
Can you add the name of the destination system (at least) on the success screen so I can remember what I…
1 voteThis information is now displayed on successful validation.
-
Include select all option for Manage Custom Filters
Selecting individual items to include for custom filters is a laborious process. We have to exclude 6000 items and we are unable to do this manually. Please add the select all option when using a filter in the manage custom filters dialog so multiple items can be selected at once.
1 voteGearset now has a `Select all` option for named items on custom filters.
Thanks for your feeback!
Thanks,
Kevin
CEO, Gearset -
Allow selecting a metadata comparison filter when editing a existing job
For monitoring / backup and CI jobs, when looking at the Metadata Filter tab, it would be great to be able to select from the Metadata Comparison Filter. Sometimes I want to be able to reapply a custom filter.
Specific example - I have a monitoring / backup job. Originally it was comparing 65 metadata items. Later, I changed the filter to compare all 96 types of metadata. Now, I want to undo my change. How do I get back to the original 65 without manually unchecking each type?
Thanks!
2 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
-
Trialforce ORG Type Support
Hey Gearset!
I want to do some testing with the Data Deployment beta feature, and i realized something. Most of my testing is done on Trialforce ORG's (Trial ORG's that are generally identified as a production type ORG). Is there a way that we can delineate between true production ORG's and a Trial ORG and have the Trial ORG as an option to deploy data to? Current options are Sandbox, Developer, and Production.
Thanks!
Richard Scott - AHM
1 vote -
Export Comparison details all items
In the comparison details the tab "all items" it should have the ability to export the table
1 vote -
When exporting from the comparison reports page, the currently selected items should show in the export
Today when you are on a comparison results screen there is an export button that will export the entire list of comparison results to a csv. However the current export does not include a column indicating items that have been selected for the current deployment. Having this column would help in reviewing the list of data outside of gearset.
3 votes -
Refresh comparison
In the Deployments > Comparison History view, there is currently the action to "View Comparison" but it would also be nice to have a "Refresh Comparison" button next to it.
1 vote -
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
-
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
- Don't see your idea?