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.
369 results found
-
When searching for a custom object name and the '__c' is included, nothing is returned.
If the search term ends in '__c', drop that when conducting the search.
1 voteYou can add __c to your search term now. Thanks for the suggestion.
-
Be able to sort/filter Validation Failures during Deployments
Like how it used to be, when I could see all the Validation Failures on one screen. I'd just Snipping Tool them, head Back to Results and fix them, quick and easy. Now the Failures are scattered within the Successes with no way to filter or sort them.
1 vote -
Enable deployment of unmanaged packages and Lightning Bolt Solutions from one Salesforce Sandbox to Another.
Enable deployment of unmanaged packages and Lightning Bolt Solutions from one Salesforce Sandbox to Another.
1 vote -
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.
-
Migrate audit fields during a data deployment
When deploying data records, it would be helpful if audit fields values could be migrated
7 votesReleased in October 2021 (apologies for the slow update of this post). Users need to enable the "create Audit fields" permission on their org before they do a deployment. Instructions here: https://help.salesforce.com/s/articleView?id=000334139&type=1
-
Have "You're Using a New Version of Gearset" Open in a New Tab
The tab that shows "You're Using a New Version of Gearset" should open in a new tab. Sometimes I click it to see the release notes and end up losing work.
2 votesIt now opens as a smaller pop-up window and will prevent you potentially losing work.
-
configure which problem analyzer results to use in CI jobs
Being able to configure which problem analyser results to use in CI jobs.
For instance, we can’t deploy any changes to managed packages because the problem analyser will ignore them (even though we have components from a managed package that we can modify and deploy without issues), that would help to reduce our manual steps during deployments.
46 votesConfiguring which problem analyzers are run as part of a CI job can be done by creating problem analysis templates and applying them to your CI jobs.
For more information on configuring and applying these templates, please see the Gearset documentation here: https://docs.gearset.com/en/articles/4942022-problem-analyzer-templates
Regards,
The Gearset Team
-
Allow for the masking of data during a Data Deployment
During a data deployment it should be possible to mask the data in specific fields. For example, if I were importing Account and Contact data from production into a sandbox I would want to be able to mask email address so that we can't erroneously send actual customers emails while we're testing
4 votes -
Ignore Unlocked Package Metadata In Comparisons
Currently, metadata from Unlocked Packages show up when comparing against an org. This leads to duplication of metadata in source control repositories (correct DX package repository and incorrect monolithic, "happy-soup" repository).
Using the Package2Member Object (Tooling API), it is possible to deduce whether or not a metadata item is part of an unlocked package. Therefore, it should be possible to ignore some or all unlocked packages (or any Package2 package), in a similar fashion to the way Gearset filters allow inclusion or exclusion of managed packages.
17 votesIn comparisons, all metadata from unlocked packages is included by default. However, some users wish to exclude unlocked package metadata from a comparison. This is so that they don't have to see metadata that they don't need to consider for their deployment.
So we’ve added this ability!
Within the packaging sidebar on the right hand side of the large filter, there is now an option to Exclude unlocked packages from a comparison. Shown in brackets is the number of distinct unlocked packages identified across the two environments.
-
GitHub Pull request
All user to submit pull request from within Gearset instead of having to jump out to GitHub.
3 votesWe’ve now added the ability to create a pull request for GitHub when the deployment has succeeded within Gearset.
You can read more about it from our blog post: https://gearset.com/blog/create-pull-request-in-gearset
-
Ability to deploy remaining Omni-Channel Components
For Omni-Channel deployments, QueueRoutingConfig metadata type is now supported by Gearset. However, corresponding PresenceUserConfigUser and UserServicePresence metadata types are not yet available. This means a secondary Metadata API tool (e.g. ANT, Workbench) or other manual steps are needed to complete an Omni-Channel deployment.
Hoping all supported components for API deployment can be included in diffs for releasing all via Gearset.
5 votes -
Export PMD rulesets/configuration as xml file
This would allow us to configure our rules in Gearset and then apply the same ruleset during our local development. Until we can upload our own xml config file, please add the ability to export the Gearset rules instead.
see related idea: https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/34668196-allow-pmd-to-be-configured-by-uploading-a-xml-file
2 votesYou can now export the pmd rules as xml by going to the static code analysis rules page:
https://app.gearset.com/static-code-analysis-rule-sets -
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
-
Support "Test Suites" for CI
Hello, Could we make a suggestion for an enhancement? For CI Unit Test jobs, could we have a Test Suite option?
4 votesYou can now specify test suites to run in CI jobs. In each CI run, Gearset will run the tests belonging to those test suites.
Feel free to drop us a message on the in-app chat with any feedback you have on running tests suites in a CI job!
Tom
-
Keep the Deployment Friendly Name / Notes when you refresh a comparison
Keep the Deployment Friendly Name / Notes when you refresh a comparison
5 votes -
Be able to add the friendly name when adding a new org
Be able to add the friendly name when adding a new org as this saves going back to the list of orgs and adding then
1 voteOnce you’ve authorized the org, a friendly name field will then become available in the dialog to allow you to also specify its name.
-
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 -
Support merge fields in outgoing webhooks of CI jobs
When sending an outgoing webhook, I'd like to be able to include if the job succeeded, the name of the job etc.
11 votesOutgoing webhooks on CI jobs now support these variables. Please let us know if there's anything else you'd like to see.
-
Output information after CI Job regarding problem analyzer skipping some component deployment
I would like to get some information from the problem analyzer after a CI Job completes as it seems like if it detects a problem during the job it skips deploying some of the components, like user permissions.
5 votesYou can now see this under [View problem analysis fixes] for each CI job run.
-
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
- Don't see your idea?