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
-
Search for test classes
It would be nice to be able to search for test classes instead of having to type them out in a comma separated list. Gearset already has such a nice search capability and it would be great if it were applied to that dialog as well.
8 votesWe have made a release to address this, can you please let us know if this matches your expectations?
-
Ability to select Field Sets as a separate item
It seems that Field Sets are deployed by deploying the object that they are related to.
This doesn't work well for me because I have admins changing objects in production, but I often need to deploy a Field Set to go with my code.
Currently, I'm jumping out of Gearset and deploying a Change Set with just the Field Sets, then coming back to Gearset to deploy my code.
It would be nice if I could select just the Field Sets and deploy them without changing anything else related to the object.
8 votesField sets are currently deployable as individual items assuming the object they belong to already exists in some form in the target. If the object the field sets belong to doesn’t exist in target yet, then it must first be partially created in the target for Gearset to be able to deploy individual sub components. Thanks for the suggestion!
-
Allow multi-selection of items with CTRL or SHIFT
It would be great to be able to select multiple items in a comparison using crtl or shift click, rather than checking the boxes one by one
8 votesReleased on 10th of Aug 2022
-
Add omni components to filters through metadata API
Now that Salesforce has moved omnistudio into standard runtime (as opposed to managed package) and also added the omnistudio components to the metadata API, the following components:
omniDataTransform
omniIntegrationProcedure
omniScript
omniUiCardSince these components are in xml format, it is much easier to see differences in source control.
It also removes the need to perform separate deployments for the Salesforce metadata API and the vlocity build tool.7 votes -
Add schedule deployment for Pipelines
It would be great to add a new feature to cherry pick and schedule deployment for the changes that have reached up till staging/uat and should be released to Prod. Without this feature it becomes difficult to manage releases to avoid downtime.
7 votesYou can now schedule deployment for a release in Pipelines.
-
Upgrade to PMD 6.17.0
Current version is 6.11.0.
We should be consistent with newer version. We are having issues with older version in Gearset regarding the ApexDoc rule.
The issue was described and discussed with Valerio in the chat.
Thanks
7 votesWe upgraded to 6.21.0 today. Thanks for the suggestion.
-
Include Test Run Details in Deployment Report for Validated packages
In the Validation deployment flow, there currently isn't a way to view test execution results if they aren't manually exported during the process. Having the ability to view the Validation Deployment report and details in this deployment flow is actually more valuable than the actual deployment report that is generated.
If we can't have that, it would be nice to be able to continue to export those test run results after deployment as part of the deployment details.7 votesYou can now access the outcome of test execution results for validated packages via the ‘View components’ menu item located under the More actions icon.
-
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
-
Allow us to configure a push notification when comparisons are done.
It would be great if we could configure a notification when a comparison completes. Sometimes comparisons take a long time!
7 votes -
Preview Deployment Details in Deployment History
On the Deployment History page, it would be nice to have a little popup window to view some of the files from the Deployment Details instead of having to download the Deployment Report
7 votes -
Be able to create a CI Job with the option to validate only (and quick deploy later).
For the case where users have committed changes to a "master" branch, it would be useful to automatically run a full validation on the new commit in the Production environment. In that way, a deployment manager can review the changes and quickly deploy a validated package that has passed all tests in Production.
7 votesHi Nghi,
We’ve added the ability to review and deploy a validation CI job.
Catherine
-
Disable scheduled tests (temporary)
We're currently using this tool primarily for nightly unit test monitoring. However, some nights we don't want the tests to run because we'll be doing after-hours upgrades and other maintenance.
As far as we know, currently the only way to 'disable' the automatic test run is to delete/disconnect the app entirely. However this is not ideal, as we have to re-add/re-auth to turn it back on.
If Gearset had a checkbox next to each org/environment that we could enable/disable the job at will, that would be ideal.
7 votesWe’ve now released support for this. From the https://app.gearset.com/test-monitoring page you can temporarily disable test jobs and then reenable them later.
Thanks for the suggestion!
-
Allow teams to share custom filters
Allow those filters we can save to be shared amongst our team!
7 votesCustom filters are now automatically shared with other members of the team and can be selected from the saved filter drop down when setting up a comparison.
Blog post on usage: https://gearset.com/blog/shared-team-comparison-filters
-
7 votes
Failed deployments are now shown on the deployment history page: https://app.gearset.com/deployments/deployed
Failed validations are now shown on the validated packages page: https://app.gearset.com/deployments/validations
-
Improve the functionality of the code diff viewer
The diff viewer could potentially have several enhancements:
- add indicators as to where the differences are in the overall file. This would give you visual feedback and let you scroll to a specific part of the document. They could also be clickable to jump specifically to the diff(s).
- Collapse by default lines that are the same to reduce the need to scroll and focus more easily on the diffs.
- Potentially offer the ability to switch between the current side-by-side view to something like the format in GitHub with differences grouped vertically.
- Add the ability to undock the diff viewer from…
7 votesWe’ve made many improvements to the diff viewer over the past year. These include, highlighting the code diff, auto scrolling to changes, resizeable diff viewer, grouping complex objects (e.g. Profiles) into logical groups for easier navigation, and Picklist rendering. Shortly we’ll be adding image rendering too. If you’d like to see any other specific additions, please submit a new idea so we can keep you up to date with our progress.
-
Partial environment variable replacement and wildcards
Some types of metadata, such as Platform Event Subscriber Configuration, have attributes identifying a user by username. As such, regardless of the value in the source environment, the value deployed to the target org must match the username pattern of that org.
For example, if the value in the source repo is <user>name@example.com</user>, when deployed to a sandbox, it must be <user>name@example.com.sandbox1</user>. From sandbox to sandbox: <user>name@example.com.sandbox1</user> must become <user>name@example.com.sandbox2</user>. And finally, when going from sandbox to production: <user>name@example.com.sandbox1</user> to <user>name@example.com</user>.
This could be solved by supporting environment…
6 votesYou can now use Regular expressions in the "Find what" field when defining environment variables, allowing you to do wildcard/partial replacements.
-
Deleted matching rule not showing as difference when trying to commit
The deleted matching rule is shown as 'deleted' in the comparison but when trying to commit and moving to the overview screen it is shown as 'no difference' which makes it impossible to commit.
6 votesThanks for reporting this bug. A fix for this was released on the 30th June. You should no longer have any issues when trying to deploy deletions of the various "...Rules" types
-
Allow me to configure my default landing page on logging in
Specifically, I use the Pipelines most of the time and would love for that to be there as soon as I login. While my use case is Pipelines specific, I would guess that others might want a different page when they login, so it would be nice to be able to configure this on a per-account basis.
6 votesWe've recently made a change to let you select your default landing page in your account settings.
-
Offer Canadian data residency.
We have clients in Canada that require data residency for data backups/deployments and even metadata deployments/processing.
Please add the option for a Canadian hosted Gearset account.
6 votesHi there,
We have now added Canada as a data storage location. You can head over to app.gearset.com - click on create new account and sign up for the same.
Thanks
Gearset team.
-
Add ability to Ignore Warnings to avoid treating Salesforce warnings as errors
See IgnoreWarnings parameter: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy.htm
6 votesWe have implemented this feature now. To toggle the setting, navigate to My Account (using the dropdown next to the Gearset logo), then Salesforce deployment.
- Don't see your idea?