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.
179 results found
-
Control When Tests are Ran Based on Metadata type
It would be nice to control when we want tests to run based on the type of changes in the triggering event for CI. Something like only run test classes on update of Apex Classes, Flows, Workflows, and Objects.
This is a bit of a patch for not having test classes fully optimized but would be helpful with orgs who have lots of profile and layout changes.3 votes -
Allow Source to choose multiple Branch for CICD Validate/Deploy
when choosing source as GitHub it allows user to choose feature/*** which allows every commit on branch name starts feature will trigger the CICD
2 votes -
Load Balancer for CI validation
would be nice to have possibility to configure 1 source (git branch), but multiple targets (sandbox), so gearset would have some "load balancer", which would distribute the validations into sandboxes, which are not busy. Its taking too much time from developers to wait for their validations to finish.
4 votes -
Deploy on pull request creation
Currently is supported only validation on pull request creation. It would be great if we can also do deployment on pull request creation, not only on merge.
2 votes -
Change Data Capture
When installing a Integration Platform you have to enable the Change Data Capture in order for the platform to receive notifications on changes. At the moment updates under Setup/Integrations/Change Data Capture can not be deployed by Gearset :-(.
1 vote -
Don't auto-select all tests when choosing "Select which tests to run"
When selecting "Select which tests to run" Gearset shows the tests included in the comparison first, but the moment all other tests are loaded, everything is selected.
When choosing this option, the tests included in the comparison should stay on top and selected, and the rest of the test should be added alphabetically but UNSELECTED.
If I'm choosing this option, I probably only want to run some tests. I think it would be much easier this way. Usually you need to run the tests included in the comparison and maybe one or two more.
1 vote -
Deploying to an org based on tags
It would be a useful feature to initiate a deployment when a Github tag is created.
1 vote -
Automatic retry for Unknown Error in scratch org creation
When creating a new scratch org from either the Gearset UX or via a CI job, one often gets the Unknown Error message
Gearset should attempt to retry this error as often, a simple retry works. This is especially important for CI jobs which should not have to be attended to manually.
Of course, the better solution is to not get this error at all
2 votes -
The option to auto-populate FLS/permissions for selected fields/objects/classes
I'd need an option to auto-deploy FLS for items i've selected in one click.
Sometimes the amount of changes is huge, and finding and clicking Permissions for selected items one by one is not a deal. For sure, it's possible to select all Permissions in Source org, and let the wizard to deselect Permissions for missing items in target, however that the result does not usually correspond to items that are in package.4 votes -
Exclude the subcomponents of the parent Workflow metadata and also exclude list views from custom objects
I want to exclude outbound messages from workflows as we will have different urls in different sandboxes. Same with list views we want to exclude them from custom objects so that we can use CI using gearset for deployments
1 vote -
create an option to have chained deployments
create an option to have chained deployments so complex deployments can be broken down and sequentially deployed or slaves can be ran
allowing for multi staged deployments under one CI job
40 votes -
Cloning deployments: add namespace option
If you are using Gearset to develop for a 1GP managed package:
Your deploys between VCS and dev orgs/scratch orgs DON'T use namespace in the metadata filter
Your deploy from VCS to Packaging org MUST USE namespace in the metadata filter - otherwise, everything in the difference viewer appears as NEW rather than CHANGED (if truly just edited during dev cycle)
So, when cloning a deployment, one should have the option to add the namespace to the clone dialog.
Without this, one has to repeat the Compare step thus losing the benefit of what you had enumerated in a prior…
1 vote -
Set time on CI Jobs instead of running every 4 hours or 24 hours
Is it possible to set time Instead of running CI Jobs every 4 hours or 24 hours.
22 votes -
Use triggering branch as source branch in git-sourced CI jobs
Currently:
We have to define a single fixed source branch in a CI job, when it has a Git-Source.Desired:
Option to say "use triggering branch". It should use the branch, where current commit-hook-call comes from.It should allow Pipelines to test also all development branches e.g. with "Validation only" CI-job.
11 votes -
Allow setting the default testing method for deployments
I want to enforce that any deployment into a UAT sandbox runs all the tests. The standard Default option runs no tests since it's a sandbox. I have to manually choose the "Run Only my Tests" Option every time I deploy to that sandbox. I would like to be able to have that option selected by default
2 votes -
Add an option to not run the comparision part in CI job (sfdx like)
When you are pushing a project with sfdx, there is no compare, sfdx just push the whole package.
It will save a lot of times.
3 votes -
Ability to carry out action after successful deployment or detect org changes (monitoring)
After every release, we have to do smoke testing. We do have automated testing using selenium and we wanted to trigger the automated testing every after release is detected. It would be nice if in the deployment we can call an api or webservice after successful deployment. Or in the monitoring we can call an api when there's a change happened in the org.
2 votes -
When validation fails, allow option to automatically remove metadata from deployment that was causing failure
It's not convenient when a validation fails, to then download the excel file of the the validation errors, view in separately form Gearset, and then go through the list of metadata I'm trying to deploy and try to uncheck each one that failed the validation. It would be nice if Gearset did that for me.
14 votes -
Save draft deployment notes
Save draft deployment notes so when you combine drafts you can see all the notes from each single draft
2 votes -
Move Package Contents to Left Column on Deployment Screen
On the "Summary of Items to deploy" page, the items in the deployment show in the 3rd column. So when you go to choose tests, you can't see what's in your package. Makes it very easy to miss a test.
Illustration: https://imgur.com/a/wbZOeiZ
1 vote
- Don't see your idea?