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
-
provide a verification that a metadata filter is to be deleted.
It's far too easy to delete a custom metadata filter. When deleted, there is no way to retrieve it. Currently, I create backups of the filter by storing them with the same filter name and datetime. It's in case someone or even myself accidentally deletes the filter.
1 vote -
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 -
Offer source branch update as option to trigger CI from custom Git (Gitlab in my case)
Please allow to select "when source branch updated" option in the CI jobs section when the source is a custom git repo
2 votes -
allow for the ability to "lock" a metadata filter in for a CI job so that the CI job has any changes to filter.
Currently, the CI job takes the current metadata filters settings but does not used the updated settings. You have to re-add the filter back to the CI job. If checked on the CI job, the job would use the current filter's latest changes rather than the ones it was created with.
1 voteYou can now edit the CI job and choose to simply refresh the filter list so it grabs the latest changes to any of the filters and as a result will let your CI job use the most up-to-date settings.
-
CI job option "hardcore" - The deployment should fail if the static code analysis identifies errors
For CI jobs we would like to have an option that validation or deployment fails when code analysis identifies any "Error" in the Static code analysis.
4 votes -
Change CI Job Design
Your new CI job design is horrible. I use disabled CI jobs as one button deployments. You've just doubled the number of button clicks I have to do for no good reason. Run Job should be on the main bar.
1 vote -
Preserve spacing in formulas!
When deploying components like workflow rules, workflow field updates, and validation rules, it would be great if the spacing (i.e. carriage returns) did not get lost after deployment. This is especially frustrating for complex formulas where care has been taken to properly indent the formula for easy maintenance.
6 votes -
Allow Migration of Data Records to Production
Salesforce CPQ uses Data for things that are traditionally done with meta-data. Due to this pricing logic, production configuration information, approval logic, and pretty much the entirety of the package is controlled with data.
Gearset has limited its data migration tool from being able to deploy data to a production org. This renders it useless when working with Salesforce CPQ and has me recommending competitors over Gearset to clients. Gearset is a better UI & workflow than other competitors, but this is a major flaw that should be removed!
3 votes -
More friendly user solution for affecting free licenses to users
Hello,
When we have 2 or more licenses and have to reaffect to a new user a license which was used before by an other user, the system disables all access to deployment fonctionalities for owner and members. We have to set all license types to "None" before being able to reaffect them to the right type of license. Can I suggest to find a more user friendly solution consisting in telling Gearset which available license to affect to which user ? Because we had to call support for finding how to solve.
1 voteWe’ve made subscription changes automatically distribute amongst users, which should solve many of the issues that users were experiencing around subscription changes.
Thanks,
Kevin -
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 -
Support of Person Account
The Data Migration function doesn't support Person Account. If Person Account is enabled, any type of Account data can't be migrated, as most of the objects have a relationship to Account object, not able to migrate Account data prevent migrating most of the Standard/Custom objects.
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
-
Compare to a Specified Source Control Folder vs. Root of Source Control Repository during Comparisons.
I would like the ability to specify a file folder when comparing a sandbox to version control. Most of my salesforce projects have a SRC folder with the contents of my package.xml. By not allowing a source folder when selecting the branch to compare, it renders this comparison useless as all files show as new. Please implement this feature to allow a directory for comparison so that I can justify using / selling this tool.
0 votesHi Ben,
I’m glad that the issue was resolved for you with the adjustment in the location of the package.xml.
Regards,
Stephen
-
View Data deployment history
Would be great to see the data-deployment history in Gearset UI. Also, the ability to replay them.
1 voteThe data deployment history page now enables you to view the deployment finished page for any of your previous data deployments.
With the ability to save a configuration template from a data deployment you can also then reapply the same configuration for the same source org in its current state.
-
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.
-
Upload Manifest File When Creating Scratch Org
When spinning up a SalesforceDX scratch org, allow a manifest file to be included. One use case is for when the Dev Hub org has PersonAccounts enabled and that feature can be enables upon creation of the scratch org.
2 votes -
Add the Deployment Friendly name to the Deployment Report
On the deployment report pdf can we add the deployment friendly name above the deployment notes.
3 votesThis has been completed and friendly names will now appear on the deployment report.
As always, feedback welcome!
-
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 -
Have a way to exclude objects from comparison
Before using Gearset we used the Force.Com migration tool. We got to learn that several things just can't be deployed to sandboxes so we always excluded them from source control, or learnt to not merge them.
Gearset has filters which mean you can specify things to include, but it would be nice to have things it would automatically exclude for you (i.e. not show in comparison). Some of these it already knows not to try and deploy. Things like
Admin.ProfileUserPermission.EditBillingInfo
Admin.ProfileUserPermission.ManageSandboxes
etc.but there's a few other random pieces that I have to remember to untick each time or deployment…
9 votesYou can now exclude specific items in your custom metadata filters in a similar way to how you include specific items.
This won’t cover some cases, such as excluding subcomponents like specific user permissions within a profile, but for those cases let’s open a new specific feature request.
- Don't see your idea?