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.
252 results found
-
Precision Deployments for Flow
Please add Flow for Precision Deployment. The new flow visualization has been really great and it would be very helpful to be able to use precision deployments with them.
20 votes -
Add navigation into elements of LWC bundle in difference viewer
The current LWC difference viewer shows the components linearly from top to bottom - meta, css, html, js. Just like you did with the side bar navigator for layout, add a side bar navigator for the LWC bundles
1 vote -
Allow users to choose their default comparison view
Different types of Gearset user will prefer to analyse comparisons in different ways. Some will definitely prefer the XML view; others will prefer the new simplified views.
I think it would be great if Gearset allowed users to specify their default view and comparisons load with this preference.
4 votes -
Show "When to Run the Flow for Updated Records" in Flow previewer
For record-triggered flows you either set the flow to run
1) Every time a record is updated and meets the condition requirements
or
2) Only when a record is updated to meet the condition requirements
It would be helpful to view these settings within the flow previewer window of a comparison.1 vote -
Show "When to Run the Flow for Updated Records" values in the flow previewer
For record-triggered flows you either set the flow to run
1) Every time a record is updated and meets the condition requirements
or
2) Only when a record is updated to meet the condition requirements
It would be helpful to view these settings within the flow previewer window of a comparison.1 vote -
Always sort results by Name (alphabetically) as a second-level sort
If a sort has been applied to any column other than Name, apply a secondary sort to "Name" so the rows always sort alphabetically by Name.
This is most useful when sorting by Metadata Type, I'd like the results to be grouped first by Metadata Type, but then I'd like to see the results sorted alphabetically by their name.
Even if the user is sorting by Changed On, for example - if there are 100 fields all deployed on the exact same date/time (ex. Mar 26, 2025 1:19pm), you might as well sort them alphabetically by Name as well
I…
1 vote -
I would expand my request to if a sort has been applied to *any* column other than Name, apply a secondary sort to "Name" so the rows always
If a sort has been applied to any column other than Name, apply a secondary sort to "Name" so the rows always sort alphabetically by Name.
This is most useful when sorting by Metadata Type, I'd like the results to be grouped first by Metadata Type, but then I'd like to see the results sorted alphabetically by their name.
Even if the user is sorting by Changed On, for example - if there are 100 fields all deployed on the exact same date/time (ex. Mar 26, 2025 1:19pm), you might as well sort them alphabetically by Name as well
I…
1 vote -
Deployment version control of Process Builders
This is for Process Builders. Add a feature to allow users to select which version of the process builder to deploy. Similar to what is available for lightning flows. I realize that Process Builders are going away. However, this feature would be helpful as many orgs sill have to manage them.
1 vote -
Customize the columns in the Compare and Deploy view, such as replacing 'Changed By' with 'Created By
Currently we cannot modify or customize the columns in the list view. So if I wish to see the records having created by instead of last modified by then there is no direct option available on UI at 'Compare and deploy'. It is really useful to have the choice over choosing the right columns as per the deployment needs.
1 vote -
Re-introduce last used comparison filter
When I start a comparison, it used to default the filter to the most recently used filter. But now it always shows as "On-Demand Comparison". Can you please restore the previous feature...it's easy to overlook that the correct filter isn't shown and you can waste time doing a comparison against the wrong filter. Adam from your team confirms "Yea that was introduced when we overhauled our comparison tool, you'll need to switch to the filter you want to use each time."
1 vote -
Fix Report/Dashboard Compares to honor RegEx "Include" on folder names (don't return ALL report folders)
Currently, if using regex to include only certain patterns for reports and dashboards, the regex works properly for the reports and dashboards returned, however, it has NO effect on the folder names. The Compare should ONLY return the folder names that match the same regex expressions if there are only include regex'es - it should remove folder names that do not exist in the regex expressions.
1 vote -
give a reminder if I'm leaving out a key piece from my deployment
When deploying a new field, not including any permissions would be strange so a reminder would be great. Think of it as a recipe. If I'm making a pastry and I don't include salt that would be odd so a reminder there would be needed. I might have high blood pressure so there's a reason I don't want to include it but a reminder is helpful. For some deployments its easier to make inferences than others but it's good to starts somewhere.
1 vote -
Side-by-side Conflict Resolution for Non-XML File Types
I would like to see the side-by-side conflict resolution that is available for XML files extended to other file types, especially Apex.
1 vote -
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 -
Version Control Commit History in Comparisons
When you compare a version control repo to an environment, it would be awesome to see the commit history get pulled in so you can quickly filter for a specific commit message(s)
0 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.
2 votes -
Multiple screens
I work with 2-3 screens. It would be great to be able to split the comparison settings to one screen and have the xml, flow navigator, lightning page visualizer,... on another screen. That way users can see more as they work. As a photographer I use Adobe photoshop and lightroom both applications allow splitting the controls and output.
1 vote -
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…
1 vote -
Cancel Comparison
I would like to be able to cancel comparison jobs so that I can totally reset the metadata selections and run it at a different time instead of making the modifications during its run time and possibly taking longer because of the changes.
1 vote -
Auto navigate to next conflict after resolve
After I have resolved a file/metadata component I would like it to auto navigate to the next item in the list.
1 vote
- Don't see your idea?