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.
1412 results found
-
Add the "cloned from" friendly name somewhere on the comparison page.
This suggestion is specific to comparisons that are initiated by cloning a package (that already has been named). Gearset / salesforce takes a bit of time to finish its comparison/validation, so often times I'll open up to 5+ tabs one for each of my gearset deployments. As the comparisons complete, I'll move between the tabs to progress through the steps, but as you can imagine it gets confusing which compare is cloned from which deployment.
Possible ways to display on UI:
When cloning a single package -
e.g.
Apps-87431When multiple packages are combined -
e.g.
Apps-87431
Apps-87431-Step2
Apps-87431-AddFieldUsually,…
2 votes -
Add an option to ignore API version differences during comparisons
When comparing Apex, and other files with API versions the difference engine will mark any files with higher API version as "changed", even if the API version is the only change. This can be undesirable when there have been bulk updates to the API version that have not been made in the development environments. It would be great if the comparison engine could make it clearer when the only difference between two files is an API version (especially when the target is on a higher API version)
2 votes -
Display auto-merged files during Conflict Resolution
The Conflict Resolution only displays files that require manual resolution. Sometimes I want to see the files that were automatically merged without human intervention.
The only way to see this is to submit a resolution as is, then read through the file changes again to look for files that were auto merged/resolved from target instead of source.
2 votes -
Allow users to select a default comparison view between 'Permissions View' and 'XML view'.
During comparisons, I constantly have to select the XML view when I click through rows of metadata as it keeps defaulting back to the Permissions View, I don't particularly find the permissions view that useful and I'm also used to XML views, would appreciate if you could give users a choice in a 'default' view to improve experience.
2 votes -
Automatic analysis for metadata
Adopt automatic validation for API names of custom objects, custom fields, custom settings, and custom metadata types. Additionally, ensure that the "Description" field is populated to enforce documentation by administrators and developers on Salesforce metadata, including custom fields, custom objects, automation (Approval Processes, Flows, Entitlement Processes), and other applicable metadata types.
2 votes -
Ability it use SOQL to provide complex filters on Vlocity and Salesforce Metadata types to create custom Compare & Deploy Filters
I would like to have the ability to enter SOQL queries to filter Metadata types and data. Currently you can only use Object or Regex when you try to filter the data to fine tune the comparison. We are looking to do this for Vlocity and Salesforce metadata types and objects
2 votes -
Filter metadata types based on whether org is licensed for that metadata or user permissions for that metadata
Compare 2.0 Metadata types
Why am I seeing Fuel Type and Fuel Type Sustainability Unit of Measure ? Running user needs a special permission set to see these metadata types and I, as running user in Gearset, don’t have this permission set.
This is an example of a general suggestion wherein if the source org/running user isn’t licensed/permissioned for some SFDC metadata, it shouldn’t appear in the (lengthy) enumeration of metadata types
Other examples are Live Chat XXX, PaymentGatewayProvider, SchedulingXXX,SustainabilityUom,SustnUomConversion, WebStoreXXX and many more
2 votes -
Soft delete User accounts
If you ever delete a user then that account can never be used again or added back. Rather than provide a warning with text that not everyone is going to read it would make more sense to not even have the delete option in the first place or do a soft delete where it can be reactivated. We have employees that have left the company and returned so its not an uncommon scenario. If someone leaves or an account gets deletes accidentally it would be nice to have some sort of recovery option then to not allow that email address…
2 votes -
Please adjust problem analyser feature to show record type changes when a picklist field value is added.
Currently Problem analyser does not show any warnings or issues when record types are not selected for a picklist field changes( value addition). With this during deployment there is fair amount of chance that some one could easily miss record type changes. Please adjust problem analyser to account this situation and show record type changes as warnings would be beneficial.
2 votes -
new comparison tool issues
new comparison method/view has a few bugs/bad ideas
when selecting a comparison pair & comparison filter on the "saved comparison pairs" page, the chosen filter does not carry through to the new screen & has to be re-applied
once in the comparison screen, there is no "sele3cted" button like on the legacy page. - this is crucial to know where I'm up to with selecting the parts to release.
2 votes -
Add support for OverrideSettings for Vlocity datapacks
It would be great if there is a way to set up OverrideSettings https://help.salesforce.com/s/articleView?id=sf.os_build_tool_override_datapack_settings.htm&type=5 for the deployment pipeline. For example, FilterFields can be specified, so those fields are removed from the datapack before being committed to the git repo.
This should help to reduce the number of differences in the compare view when e.g. Salesforce IDs are different or empty attributes are added.
2 votes -
2 votes
-
Delta comparison between two unit test reports
Hi team. Would be good to have a feature that allows us the comparison between two unit test results. We are interested to export the delta errors from one day to another.
Use case: We are executing deployments for more than 50 pull requests against the same target sandbox, hence regression errors might be introduced throughout the day. We are running nightly unit test jobs and usually, in the morning, we have extra tests which are failing comparing with the previous day.
We are currently exporting the gearset errors from 2 reports, in Excel tables, and compare these ones to…
2 votes -
Show Created by and Created Date in Comparison view
I'd like to see created by and created date in the comparison view. Sometimes we have multiple users working on items and I may not be the last to modify something but I am the one to deploy it and if I am the creator, I know what it is named but it makes it hard to sift down if I can only show modified by and modified date.
2 votes -
Change Order of Steps for Data Deploys
When configuring a data deployment, currently "Planning Deployment Steps" is the last step, but this is where I often encounter the "Error while planning deployment" because of recursion/etc. That means I need to back up through the previous 4 steps, adjust, and then go BACK through the related objects, data masking, disable rules steps before it will try again.
The disable rules step in particular takes some time, making this a really tedious cycle to repeat.
I understand needing the related objects step before validating the deployment, but if the order changed to:
- Select Objects,
- Select Related Objects
- Plan Deployment…
2 votes -
Gearset Unit Test Monitoring ignores test methods in classes at V27 or earlier
For older orgs, one may have Apex classes at V27 or earlier. Such classes were allowed to also include testmethods.
Gearset's Monitoring job ignores these test methods leading to a false sense of security that one's org is "correct"
Example class is at V24
class Foo {
void doStuff() {}
static void testmethod myTest() {
new Foo().doStuff();
System.assert(...);
}The myTest will not be run by Gearset Unit Test Monitoring. It will be run by Setup > Apex Test Execution > Foo > Run tests
2 votes -
Help users Deploy Sales Cadences between orgs
Sales Engagement for Salesforce allows users to build Sales Cadences. These seem to be record based, so being able to move these between orgs would be great.
2 votes -
having a Release Manager role within a Gearset team
I want the ability to set specific users as release managers and only these users can deploy to a production org. Only this role should be able to create a direct authentication to production. Other roles should be blocked to create a direct authentication to production or blocked from selecting production as a target org.
2 votes -
Allow download of XML files from the comparisons page
In some instances, we have to use the Metadata API to download XML files for analysis. However, the Metadata API is a pain to use. Even Salesforce recognizes this and suggests using a migration tool like Gearset to extract these: https://developer.salesforce.com/docs/atlas.en-us.246.0.api_meta.meta/api_meta/file_based.htm
Since Gearset retrieves these files during comparison, it would be great if there was an option to download them to a zip file directly.
Note: There is already a "Download Package" feature on the deployment page. However, we obviously can't add items to this page if there is no change between the orgs. So, if a similar feature were…
2 votes -
Ability to use include/exclude patterns for Apex tests
Now we can only have patterns to match test classes to include.
Would love to have ability to use include/exclude patterns (like for comparisons).
We have many tests which we don't want to execute within CI jobs. These could be from (stable) 3rd party libraries like FFLib.2 votes
- Don't see your idea?