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.
262 results found
-
Support aliases for metadata types in the search box
So often, I type something in the search box for a metadata type based on the point-and-click force.com labels and the search comes up with nothing.
I'd suggest an auto-substitute option so if one types in 'Email alert', it auto-prompts for the metadata API substitute: 'Workflow alert' Or, if one types in 'Support process', it auto-prompts to substitute 'Business Process'
1 vote -
Filter out Custom Field differences based on Field Tracking History
If the only difference in the field is that History Tracking is turned on, it would be nice to filter these results out.
Running checks on our app with multiple customers, who all set history tracking differently, can create a lot of noise to filter through to find actual differences.
3 votes -
Add a validation/warning for when users try to filter only permission set for comparing and deploying
we believe that if we are given the option to filter only permission sets for the comparison, there should be some type of validation ensuring that you are also including dependencies such as custom objects, apex classes etc so that we don't make the assumption that filtering permission sets only in the comparison will include all dependencies
1 vote -
Filter standard vs custom objects
We sell a managed package and will never include standard objects in a comparison, and absolutely not in source control. When I'm running a compare against source control to check for changes, it will show all of the standard objects as "custom objects" which is not correct. I should have a way to filter out standard objects from the comparison.
1 vote -
Improve comparison performance
If there is one thing that is :-( about Gearset is that for moderate size orgs (a few thousand objects), the default 64 comparison takes too long.
You want to initiate a deployment from source to target and, for whatever reason, you want to make sure you didn't miss anything that needs to be deployed
So, to be safe, you initiate the 64 default comparison.
And you wait (downloading, comparison). This can take several minutes. You go on to other tasks and your zeal to get the deployment done went off onto other things as the comparison time is too…
4 votes -
Have a timer on the compare page to indicate how long the compare is taking
Sometimes a compare can take us 30-45 minutes depending on the complexity of the org. I would like to see a running timer on this page of how long the compare is taking. I don't expect it to say how long is left, just how long it has taken so far. This will help to highlight if any abnormalities are happening, ie. if it's taking a very long time and is only at the Downloading phase for example.
4 votes -
Enhanced Comparison filter - filter by difference count
My use-case would somewhat be handled by separating code and xml differences, but I would like to be able to filter on difference count (or at least, easily see / sort by diff count).
For example: We are updating the API version on all of our classes and triggers (about 279 files this go around) and I want to make sure that the API update is the only diff when doing a deployment. Or to be worded differently: only deploy files where the only difference is the API version.
1 vote -
Support deleting comparison data
Having the comparison history is a great feature, but it would be very beneficial to be able to delete any data in the system, especially when working with a trial account. Part of testing could include working with test environments that you don't want to persist after going live. Also, peace of mind when ending the trial that your data has been removed.
4 votes -
Warn if a selected metadata type is not supported by selected API version
In the custom filters dialog, if you select a metadata type that is not supported by the API version, the compare and deploy currently just silently ignores that item, giving the impression that the compare has failed. e.g. selecting "Duplicate rule" with metadata version prior to 38.0.
It would be good for Gearset to provide a warning if a selected metadata type is not supported by the selected API version.
2 votes -
Suggestion - make comparison highlight colors configurable
The background highlight colors for differences are much too light to be able to be seen clearly when viewing in APEX mode. Colors are much brighter in XML mode. Request - allowing these colors to be configurable. Thanks for the consideration.
1 vote -
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 -
A count of differences could be grouped by type
If the count of differences could be grouped by type/color that would be helpful.
Ex: 20 differences: 5 red, 7 green, 8 yellow. It gives a better sense of how drastic the differences between Source and Target are at first glance.3 votes -
When the difference between Source and Target, on a particular line, is only in the formatting. Highlight in a different color
From what I can determine you are categorizing the differences as follows:
Code in Source, not in Target – Highlighted in Green
Code in Target not in Source – Highlighted in Red
Difference between code in Source and Target – Highlighted in YellowWhen the difference between Source and Target, on a particular line, is only in the formatting. It would be nice if that was highlighted in a different color than yellow (perhaps grey). It would speed up the review of the code knowing a certain color was only a formatting difference.
13 votes -
Include both dates on comparison export
The sheet exported from a comparison currently includes only one date column. It is unclear which org this refers to. It would be great if it included two columns (one per org) so that one didn't have to individually look up the item to determine which version is newer.
5 votes -
Initiate comparison from package.xml
I'd like to be able to drop a package.xml file on the New comparison screen. Doing that will have two effects.
First off, it will drive the selection of which metadata types to include in the comparison.
Secondly, it will automatically select the components listed in the package.xml on the comparison results page.
This provides a really good way to expediting a deployment, since package.xml are used pretty universally by both IDEs and standard deployment tools (including packages).It also helps me take advantage of the intelligence of automatic dependency and all of the other goodies that Gearset has. Basically I…
22 votes -
Dependency Engine enhancement for Sharing Rules
Dependencies with sharing rules. Roles/Groups/Fields referenced in sharing rules may be helpful to add as "dependent" on as if they are not in the destination org you cannot deploy.
2 votes -
Scroll to top of category, when switch between All Items, Changed Items etc
Just a user preference item – when you switch tabs (ex: New Objects to Deleted Objects), it doesn’t place you at the top of the window.
So if I scroll down through all the New Objects and then switch tabs to the Deleted Objects, it just places me in the same relative location as I was in the New Objects tab.
It would be nice to have it reset to the top of each window when I switch tabs.
2 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 -
Unselect all standard profiles & related permission
Often you want to deploy Admin profile and (x) custom profiles. Compare and deploy picks up hundreds of entries for standard profiles which are surplus to requirements. A single click way would be veryuseful.
4 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.
- Don't see your idea?