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.
7 results found
-
Permission set changes not displaying without drilling down
You shouldn't have to drill in to see the changes in a permission set. I was stumped b/c it showed no difference, but in reality I had to drill down to see the difference. This is bad UI
9 votes -
Create releases in Pipelines not at final stage
Right now you can only create releases at the last environment in a Pipeline. We'd like to have 2 stages so we have a true dry-run of deployment. Our pipeline is
Dev > QA > UAT > Staging > ProductionCreation of the release branch before Staging would allow us to effectively cherry-pick what we want deployed into Staging as we get UAT approvals, do a test deployment where QA does a sanity/smoke test and have greater confidence when we get to our Production release.
11 votes -
Select All Option in Deployment history
It would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target.
2 votesThis is now possible as long as a filter is applied to the deployment history page.
-
The ability to deploy only certain fields in a record type and not all fields
If we want to promote a change to a single field in a record type, we're unable to because the file is pushed in it's entirety. We'd like the ability to view from list of available changes in a record type by field and select just the changes to the fields we want to promote.
3 votes -
Allow individual lines to be selected for inclusion or exclusion of a deployment
Allow individual lines to be selected for inclusion or exclusion of a deployment
47 votesEDIT:
Gearset now lets you select specific fields in layouts for a deployment.
Here's a quick article on getting started with precision deployments for layouts:
https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
We are working on adding support for more metadata types such as record types, value sets, Lightning pages and other XML types.
-
Support for WaveXmd metadata is missing
If we replace default DataSet in Einstein Analytics, it creates another type of metadata "WaveXmd". Support for the deployment of this metadata is missing from Gearset and as per discussion with Gearset team, it's a bug. Could you please fix it.
2 votes -
Provide an option to run Aura and/or LWC testing before deployment
I don't think that very many people are actually creating Aura/LWC tests yet, but they really should be.
Since SF doesn't require them like it does for Apex, if we decide that those tests ought to be run before deployment, it would be great to have Gearset run them. This will help us to make sure they are run before every deployment instead of relying on developers remembering to do it manually.
5 votes
- Don't see your idea?