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
-
Allow scheduled jobs to be assigned a different authentication user
We would like the ability to change over scheduled monitoring/testing jobs to a different authentication user. Currently if we need to switch an authentication we lose the history.
Consider:
I leave my employer and I need to switch the monitoring over to another developer or admin. I have to delete all the current scheduled jobs and re-create them using the other users authorization. Which causes the history to be lost.11 votesThe feature was completed. The documentation is at https://docs.gearset.com/en/articles/3758806-transferring-ci-job-ownership
-
Add a `Weekly` cadence to the test runner
I need to run my own tests (ie no namespace) daily as those should never fail and if they do I need to know
For namespace tests, I just need to run them weekly, primarily to reset the "invalid" flag on apex classes that can be tripped by trivial changes. I know some will fail as we have some huge apps installed and my understanding is that it's normal for dome of those managed tests to fail.
So I would only want to run them weekly to reduce the noise from the daily failure email. Just run those on Saturday.
11 votesYou can now schedule unit test jobs to run on specific days of the week, which means you can set up a weekly cadence setting the job to run on a single day.
-
Ability to activate / deactivate Flows / Processes as part of the meta data and/or data deployment process
It should be possible to have gearset to deactivate flows and/or processes based on a selection. And to roll-back afterwards. Similar to what has been created here: https://sfswitch.herokuapp.com/
10 votesHi, thank you for voting on this UserVoice.
Flows can now be deactivated in Gearset alongside validation rules and triggers before data deployments.
Click the View and disable rules... button in the bottom-right of the pre-deployment summary page (next to DEPLOY DATA) to prepare a special metadata comparison.
To deactivate a flow, simply select & deploy its corresponding flow definition.
https://docs.gearset.com/en/articles/4536761-disabling-validation-rules-triggers-and-flows
-
Update CI Job History Exports to include User and DateTime Stamp
In the CI Job section under the view history button, when selecting the ability to export the changes, Is it possible to include a DateTIme stamp
and User column for each row change?10 votes -
Deploy single layoutitems
In Layouts there are multiple layoutItems. it would be helpful if we could to deploy single <layoutItems> from a Layout without affecting other <layoutItems>.
10 votesYou can now deploy single layout Items using Gearset's new Precision deployments feature: https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
-
Ability to Clone Button on the Draft Deployment page
Can you create a Clone Button on the Draft Deployment page similar to the Clone Button on the Deployment History page? Some times we collaborate on a deployment and one user will take over. We want to be able to deploy the package as the current user, not the original one that made the draft.
10 votesThe ability to clone draft deployments is now available on the enterprise tier.
-
Be able to require a commit message for deployments
Sometimes a user may forget to add in a commit message before deploying, so the history in our source control is "no commit message" which is not editable. Can we add a feature to be able to turn on marking commit messages as a requirement for deploy?
10 votesThis has now been shipped.
The team owner can now enable deployment notes to be required via the setting located in the account summary page.
-
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
-
Org metadata snapshots
Allow a snapshot/backup of an org prior to running a deployment. Allow us to use this as a source of a new deployment if we want to revert any changes previously deployed, or at least download the package.
10 votesThis feature is now available. You can take snapshots of your metadata on-demand via the Change Monitoring feature and download the zip file created.
Use the local files option when configuring your comparison.
-
Allow users to choose when change monitoring and unit testing jobs run
The change & test automation is great, but we can't choose when these jobs run. The option to choose when to run jobs so they don't coincide with dev work would be a great addition.
10 votesThis has now been added to both change monitoring and testing jobs.
-
Provide support for deployment and object dependencies
Gearset Deploy should provide a way to show any object dependencies before a deployment is due to take place.
10 votesDependencies are now available, and you’ll be warned when you try to deploy an object without its dependencies.
-
List the unit tests failures in the email notification being sent out
Currently, when the unit test job fails, we can view the test history and results by going to the web page. However, we would like to view the summary of unit tests that failed in the email notification that is being sent out.
9 votes -
Ability to run a Validation only CI job on a pull request - this will make pull request ready for deployment without error
- Developer creates a pull request to a branch
- CI job validates the pull request and notify in case of errors
- Developer corrects errors - CI job again validates the pull request and this time it is fine 4.Release manager merges the pull request to the branch specific to an org and CI job deploys without error.
9 votesWe now support validating pull requests from GitHub, GitHub Enterprise, Bitbucket, Bitbucket Server, GitLab and Azure DevOps.
-
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.
-
Be able to edit the CI sync frequency
When creating new CI job from one Salesforce org to another, there is no way to edit the frequency of synchronization. It would be useful to make a change so that integration is done less often than every 4 hours
9 votes -
9 votes
You can now export the results of the static code analysis as a csv file from the main deployment workflow, change monitoring results for an org and CI job runs.
-
Include/exclude individual metadata in templates by managed package
The Include Managed Packages option right now is a global one-- and, while nice, that doesn't cover situations where you want some metadata of a Managed Package (eg. a Profile permission) to be included, but not others.
Currently users have to laboriously deselect data related to Managed Package in certain areas (eg. Static Resources, Permission Sets, Custom Tabs) because it'll always fail to deploy.
The ability to include Managed Packages for some metadata, but not others, in templates would solve this issue.
9 votesWith Gearset’s named filters, you can now configure exactly which metadata components are going to be included in a comparison.
For the advanced use cases, you can also use regular expressions to define rules that, for example, include all managed components that match a certain naming convention.
You can find the docs on our site https://docs.gearset.com/feature-guides/comparisons-and-deployments/custom-metadata-filters
-
"Run now" button for test automation
Adding the ability to kick off a test job on demand, rather than the daily or configurable frequency
9 votes -
Add batch size option to data deployment
It would be great to be able to pick the batch size used when doing data deployments.
We have to work with some orgs using poorly performing managed packages that are blowing up due to CPU limits.
We don't have many option, so being able to reduce the batch size, and hence the CPU load would be really useful.
8 votesThis now completed and can be set at a team level at https://app.gearset.com/account/data-settings
-
Create the ability to migrate components to new source and target orgs after having in a Saved Drafts.
When saving components into drafts, when validated, we would like the ability to be able to migrate the same components into new source and target orgs.
8 votesHi,
You can now use the new clone feature for any saved draft deployments if you’re an enterprise tier user.
Regards,
Stephen
- Don't see your idea?