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.
247 results found
-
Improve PermissionSet comparisons by providing an option to ignore fieldPermissions when their editable/readable are set to false
Current Metadata Behavior:
When a new object is added, objectPermissions are only added to a PermissionSet only if one of allowCreate, allowDelete, allowEdit, modifyAllRecords, viewAllRecords are set to true
When a new field is added, the new fieldPermission is added to all PermissionSets by default (with editable and readable set to false).
NB. PermissionSets are additive in behavior and can only open up access not revoke. Values of false have no meaning and are only noise.Current Gearset Comparison Behavior:
Comparing PermissionSets show these new fieldPermssions as New Items even when default values for editable, readable are set to false.…9 votes -
Permission set changes not displaying without drilling down
You shouldn't have to drill in to see the changes in a permission set. I was stumped b/c it showed no difference, but in reality I had to drill down to see the difference. This is bad UI
8 votes -
Cleanup Layout Assignments
When you rename a Layout, the previous Layout Assignment won't be cleaned up on the Profile.
This should be cleaned by the Repo dependency cleaner.8 votes -
Compare metadata by "Changed Date" for both "Source" and "Target"
In "Compare and Deploy", is there a way to add a column for "Changed Date" for the Source item, in addition to the Target item?
I want to select all the items which were more recently changed in the Source than in the Target. In my current large org compare-and-deploy, I see many items which are different but the one in the Target was more recently changed, so I don't want to overwrite that item in the Target.
8 votes -
Add option to suppress managed custom fields in comparison results
When comparing Custom Objects that contain the managed custom fields there is no way to suppress the managed custom fields. The fields would show up in the comparison results even without being requested. The problem analyzers then highlights and remove these managed custom fields.
This is cumbersome when repeated and makes finding genuine differences we care about more difficult.
From the problem analyzers, it sounds like Gearset is able to identify the managed custom fields. Therefore could there be an option under [Include managed package] in the Custom Filters that allows the suppression of known managed fields in comparison results?
8 votes -
Here's the best solution: Be able to quickly select the custom objects and standard object custom fields AND only the related metadata items
Would like to be able to quickly select the custom objects and standard object custom fields AND only the related metadata items to make then function correctly (permissions, layouts, field level security, etc..)
Then we could go back and migrate all the process automation stuff - workflow rules, flows, trigger, etc..
It always starts with the data schema first. We need a quick way to see what is different between two orgs and get that synced first
8 votes -
Namespace Mapping for Managed Packages
We are an ISV partner with a managed package we sell to lots of customers. That means our package is namespaced. However with a distributed development team and multiple dev orgs, all source code is not namespaced, and is maintained in source control (github) without namespaces. Only upon unit test and promotion to the package org, does the namespace get added. This results in two basic problems (and others). 1) comparisons between unit test and package result in almost everything being flagged as "changed" due to the namespace, and 2) all aura components are always flagged as "new" when they…
7 votes -
Save previously entered comparison filters
I am currently using a standard regex filter each time I do a comparison. It has become quite lengthy such that I can't easily remember it. I have ended up saving it in a separate text file and have to open it, then copy and paste it into Gearset each time I do a comparison. Pretty cumbersome.
It would be nice if the Filter... text box on the comparison results screen was a combo box that when clicked, dropped down a list of recently used filters. Each entry in the list should be removable (like with a little 'x' icon…
7 votes -
Differentiate XML and Code differences in the comparison
I would find it very useful if the comparison result highlighted if the difference was in the XML or the Code (or both) for each item. This would especially save time when there are a lot of differences.
7 votesThanks for the suggestion Celio.
We think this should be possible to do and are doing some background work into how to manage and display this. More details to come soon.
Thanks,
Jason. -
Allow for Scheduled Comparisons
Like Monitoring Jobs, allow users to choose a source, target, and metadata filter, and schedule when a comparison runs.
The primary goal of this would be time savings. To have that data already retrieved and cached so you can go in, make your selections, and move toward deployment more quickly. Possible applications include recurring deployments, planning out your workday, etc. This addition would be for non-Integration users.
6 votes -
allow selecting of specific picklist values when deploying changes to picklist fields
Essentially would like to be able to cherry pick the values for a picklist value that is being deployed from a lower sandbox. Basically what you did with Precision Layout deployment for page layouts. There are times when we do not want to deploy all of the new/different values for a picklist field.
6 votes -
Inline editing of metadata
The idea above was "closed" due to Environment Variables.
That feature is too fiddley for our use case as the change that needs to be performed is not consistent. Furthermore, that feature does not help with handling merges.
Gearset has some merging capabilities, but it only allows to select one file or another, instead of merging changes from both files.
I'm aware it is possible to perform merges from source control, though it would be easier to train our team if they did not have to learn another technology. Furthermore, it leaves the process to more faults as the…
6 votes -
Add a 'flag' to ignore XML 'utf' versus 'UTF' in XML header.
I believe there exists a mismatch with the XML header reference to UTF in the Gearset library to what is used in SFDX.
6 votes -
Options to pick only selected custom labels metadata for salesforce.
Since the custom labels metadata can’t be picked individually, the Gearset compare and validate process would pull in all custom label changes. This would be a concern if we want to withhold any particular custom labels from being pushed to higher environment.
6 votes -
Display the Filter used in the Comparison history screen
It would be helpful in finding the right comparison to look at if you could see on the Comparison History screen which filter was used. It would also be helpful when looking at the comparison details to know which filter was used.
6 votes -
Filter on selected items
I want to quickly be able to identify components that have not been reviewed by only seeing unselected items in the "Changed items", "New items" and "Deleted items" top level filters.
seeing the ones I have already selected slows down productivity and I have to scroll through them. If I want to see them I can always look at the "All items" section. This information is also available in the difference type column.
6 votes -
Add support for Vlocity managed package vlocity_cmt__ProductConfigurationProcedure__c object
Add support for Vlocity managed package vlocity cmt ProductConfigurationProcedure c object. Currently it is not supported by Gearset Vlocity tab. Confirmed by Gearset. This limits the autonomy of products deployment for Vlocity projects.
5 votes -
Saved Comparisons should be visible to team members
I have a team that has access to Gearset but unfortunately they cannot view the Saved Comparisons I've created. To reduce unnecessary time spent on creating and maintaining Saved Comparisons, it would be greatly appreciated if the Saved Comparisons could be shared with the team and possibly allow the owner to delegate access to the Saved Comparisons.
5 votes -
Ability to cherry pick changes in a file
When comparing changes between a source org and a target org for a given file/metadata component, it will be great to have the ability to choose which change(s) should be promoted from the source org to the target org.
Presently, it's an all-or-nothing scenario i.e. either one deploys all the changes to a given file from source to target or deploys none. As a workaround, we cherry pick changes to a file using VSCode and then deploy to the target org using VSCode –– which is the exception to our "all metadata changes must be deployed through Gearset" policy.
Adding…
5 votes -
Ability to choose whether or not to respect the forceignore file
Would like a checkbox on the comparison screen that allows me to choose whether or not the comparison will respect the contents of the forceignore file. (Similar to the checkbox allowing you to choose whether or not the comparison should use the package.xml file).
Our usage of Gearset does not align with our usage of the forceignore file for automated deployments. In fact, we often use Gearset to manually compare and/or deploy items that we specifically ignore for automated deployments.
Summary of problem this new feature has introduced:
We use gearset for org -> git deployments, and for git ->…5 votes
- Don't see your idea?