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.
270 results found
-
Better pre-selection of repos & branches
My reasoning for the need:
Every day when comparing, I have to choose one github repo out of 343 (46 of mine + 297 from an org I'm a part of). Yes I know I can type some characters and it will search the list of repos, but it's still unpractical. It sometimes looks like it remembers the choice, but I think it doesn't quite work after logout and I have to select the repo from the long list too often.The bare minimum that would bring me pleasure:
The last used repo I used for any comparison would always…4 votes -
Default to Object View
Option to default to Object View vs XML for metadata types that have it available
9 votes -
FLS selection for Source control
while deploying a field to source control. we just want to move profile FLS of that only field. FLS was not displayed on the components drop down of profile. we are only able select profile so that whole object's FLS are getting deployed to the Source Control.
5 votes -
Selection Count Mismatch
The Selection count on ‘Compare and Deploy’ page doesn’t match with ‘Items Selected’ on ‘Draft Deployment’ when a draft deployment is opened. Having this in sync will help user that all selections are going in the deployment.
1 vote -
Need a Lock to the Custom comparison filters
We need a lock to the custom comparison filters so that the team will be on the same page and only the deployment manager can be responsible for all the deployments
3 votes -
Be able to exclude single items from comparison
E.g. If I generally want to include all Custom fields for all Objects in the comparison, but there’s one specific field that I don’t ever want to send across to the target org, it’ll keep popping up and I’ll have to uncheck it each time.
1 vote -
Track Items Added to Draft Packages
It would be nice to be able to see which items within a comparison are part of Draft Packages. We have a need to build multiple packages from a single Comparison of Instances. This can be done by creating many Drafts, but it is sometimes difficult to know if items have been added to a draft package already. If we could visually see this, it would allow us to generate and confirm our packages much faster.
1 vote -
Search for components within Profile should show results regardless of expansion of specific profiles
Use case on Difference Viewer:
search on `profilerecordtypevisibility' (or use metadata filter and check Profile: Record Type Visibility)
Results
Unless the difference viewer already has the Profile(s) expanded for their components, you get no resultsDesired behavior -- Search on components within Profile should show results; even if search takes longer
4 votes -
Allow XML package for org snapshot/daily monitoring
Allow XML package for org snapshot/daily monitoring. This is to take the previous day's design to be downloaded in xml format that we can open in eclipse IDE.
1 vote -
would be cool to be able to "ignore" certain differences
would be cool to be able to "ignore" certain differences... e.g. encryption. So if encryption is enabled in a Production Org but not in a Sandbox (not sure if Encryption is possible for SBs), you have a difference for every custom field <encrypted>true/false</encrypted> which is really irritating.
18 votes -
Difference Viewer custom object name: include suffix __c, __x, __mdt, __e, etc
When you look in the Difference Viewer, it is not clear at all by inspection which line of Metadata Type "Custom Object" is a standard object, custom object, platform event, custom metadata type, historcial trending object, etc.
For example, Custom object Foo__c displays simply in the Name column as Foo. This is a loss of information in the difference viewer, especially if one has similarly-named custom object metadata types such as:
Fooc
Foose
FooConfig__mdtthese display as
Foo
Foos
FooConfigThe full Sobject Name gives the user hints as to perhaps other related components that need to be…
3 votes -
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 -
Ability to manually hide/filter component differences by single flag
When reviewing comparisons it would be extremely helpful to have the ability to manually 'hide' a component difference (e.g. a single flag to filter out, ignore, or even 'grey' a component differences) once you have a) reviewed the XML and b) determined you do not want to deploy or view that component in a saved draft. I.e. a third state that is not simply 'selected' or 'deselected'.
Current filters by component type, name, et al. don't accommodate for wanting to hide a known component difference (e.g. like an Apex class still under development) so that you can only see remaining…
2 votes -
Show # differences found in comparison display
It would be a nice feature to see the number of differences for each item from the perspective of the source org vs target org.
3 votes -
When a Picklist Populates, Don't Default to the 1st Value, Default to Blank
When I choose my destination, the system defaults the picklist to the first item on the list. Instead it should populate the list but don't pick a value.
For example, when I choose destination = BitBucket, it then takes a moment to load available branches. It takes a little bit so I go on and start to configure the metadata types. Meanwhile, Gearset populates the list and sets the value to the 1st branch on the list, in my case, feature/helpdesk. It should leave the value blank and make me pick.
This has resulted in me running long-running comparisons, and…
3 votes -
Simple visualization showing Process Builder differences
Assuming the high-vote count Idea for matching on latest version Process Builder flow between source and target (and not by version #) is implemented; make the visual comparison between source/target PB not solely XML.
Process Builder in XML can't be deciphered by a human mind. Hence, a simple indented text-based visualization could be done to make it more readable
- Decision 1.1 Entry criteria 1.2 Immediate actions 1.2.1 action 1 details (XML here OK) 1.2.2 action 2 " " 1.3 Scheduled actions 1.3.1 scheduled action 1 (XML here OK) ...
- Next decision ...
There's an implicit tree layout in the PB…
3 votes -
Display "Metadata comparison (custom) filter" used on "Comparison in progress" -screen
Hi! I just started to evaluate Gearset. Looking good. When I was staring at "Comparison in progress"-screen this came to my mind:
Sometimes it takes a bit longer than expected and I start to think: "OMG - What custom filter I used? - Probably I'm comparing everything - That's why it takes so long - Maybe I should cancel this job?".
It would be more reassuring if the Metadata comparison (custom) filter being used was also shown on that "Comparison in progress" screen.
4 votes -
Show filtered counts on the results grid tab titles
When comparing two orgs. We need to show the eaxact number in the Tabs(Changed Items, New Items) when filtered.
2 votes -
Show Workflow Activities As Dependency of Parent Workflow
When selecting a Workflow Rule, its dependent components (i.e., email alerts) are not shown in the dependency view. They should be.
2 votes -
refresh comparison UX - echo the filter used in the original comparison
When you click Refresh Comparison, the dialog does not echo anywhere the original filter name used in the comparison-being-refreshed. You just get a x/y filters being used.
Always good to remind the user as to which filters were originally selected without having to scroll through the list
1 vote
- Don't see your idea?