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.
267 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 -
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 -
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 -
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 -
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 -
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 -
Allow for Simplify Differences to be performed on metadata type before showing it as "different"
Currently, Gearset performs a "Simplify Differences" on Clean data service and
Connected app before reporting these metadata types as "Changed" in the comparison results.There are other metadata types, such as "Custom field" that sometimes show up as "Changed" in comparisons because the internal order of some of the tags are different in a sandbox vs production. Re-deploying these files from one environment to the other does not "fix" these differences. Gearset provides a "Simplify Differences" toggle in the UI that shows there is no effective difference with the file.
It would be nice to provide a configuration toggle for…
3 votes -
Allow Adjusted Column Sizes to Persist in the Comparison Table
Have adjusted column sizes persist once they've been adjusted in the comparison table instead of resetting with each selection. Deploying changes to permission sets could be dramatically streamlined if it's possible to maintain resized columns. If column sizes were set to accommodate the name instead of giving them all the same size, that would also be a huge improvement. The other columns don't include as much info as the name column so it's a waste to give them so much space. It is also inconvenient to caret down in permission sets especially when looking for multiple fields in one permission…
3 votes -
Compare Types on Comparison
For the pipelines observed when creating a feature branch and during comparison runs, a default filter is applied to the compared types without any metadata types selected (0). We would like to have a custom filter with metadata types for a specific pipeline pre-selected by default when the feature branch initiates the comparison.
3 votes -
Save sort order in Saved comparison pairs
It would be nice that the chosen sort order of the saved comparison pairs could be saved.
If I choose to sort the saved comparison pairs on Friendly name and i open a new tab of gearset, the saved comparison pairs in the new tab are sorted on last used. It would be nice that in the new tab, the saved comparison pairs are sorted based on the same column as the previous tab.3 votes -
Split Lightning Page Metadata Type
Think the Lightning Page metadata type needs to be split into 2 categories. Reason being it is the one metadata type that causes comparisons to run for extremely long times or even crash/time out. This happens because it trying to compare all of the lightning email templates users make. It would be better if lightning email templates were their own metadata type and the lightning page type was actually just lightning pages created for objects.
3 votes -
Make filter to search through all the components which are hidden under 1st level and expand the components
Can I ask Gearset team to add filter in compared components to search through all the components which are hidden under 1st level (e.g. custom objects or profiles).
For example, in the filter to compare metadata I selected certain custom tab (in the profile the access to the tab was deleted), also selected certain profiles, but serching through the compared metadata list I spent hours and did not manage to find those components for deployment package.
The same is for object access. I selected certain object, selected certain profiles - and again, it's a hard quest to find necessary components…3 votes -
Ability to Filter Out Namespaced Metadata
I figured the best way to write this out was in the form of some sub-par user stories.
As a Salesforce Admin, I need the ability to do a comparison of two orgs/repos and have it show only non-namespaced metadata so that I can easily distinguish between things I own and manage vs what are from managed packages.
As a salesforce Admin, I want to be able to indicate that I want to hide all namespaced metadata while still being able to show custom fields I create on a namespaced object so that I can quickly deploy new custom fields.
…
3 votes -
Allow Record type additions and removals to be selectable
I am not a having an option to deploy the particular picklist values in the Record type level, I would like to include only the values I have added that are different from my target environment.
3 votes -
Ignore Business Owner changes between Sandboxes
This was marked as "Completed" in https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/39507649-resolve-data-owner-user-metadata-from-difference
But really the issue remains.
When "Business owner" is populated in a field, it will show as "different" since the XML is showing username, which is different between sandboxes.
This make trying to do comparisons to find differences very challenging.
3 votes -
comparison between 3 or more ORGs
i would like to see in a future update about comparing 3 or more Orgs to possibly fine tune checks between production, and multiple sandboxes to make sure everything looks as needed to verify no sandboxes are overlooked for refreshes if needed.
3 votes -
Meta Comparison Filter Based on User and/or Timeframe
It would be great if there was a way to create a metadata comparison filter, and not just filter with regard to metadata types, but also filter by which user made the change, or the timeframe when the change was made? For instance, it'd be great if I could create a filter based on changes I made within the past 30 days, or a specific timeframe. Filtering by metadata types takes very long for large orgs, even if I reduce the metadata types down to 1 or 2.
3 votes -
Add the ability to run the problem analyzer while on the comparison screen
I originally was going to request the ability to append the items found in problem analyzer to the list of selected components, when going back to view the comparison, but then I thought why not take it one step further, and move the problem analyzer feature to the comparison screen? Then, the items it finds/suggests, the user can add them to the package there, or choose to ignore them.
3 votes -
add the option to either hide source control locations where you do not have a connection, or allow a default SCM connection to be selected.
We only use on source control service, so having to select 'Azure DevOps' before being able to select the repo/branch, is a small step that adds up over time.
Being able to either hide services that you do not already have a connection for, or being able to default to a service, with the ability yo navigate back up and over, as needed. would be welcomed.
3 votes
- Don't see your idea?