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.
245 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.
14 votes -
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 -
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.
1 vote -
Auto-scroll simplified comparison views to the first difference
When you view a comparison using the XML view, Gearset automatically scrolls you to the first change in the XML file.
However, when you use the simplified view, which is now the default comparison experience, it does not automatically scroll, and you either have to use the Next icon (an extra click every time) or do a lot of scrolling.
I would like to request that the simplified comparison views also scroll to the first difference.
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 -
sidebar
Love the comparison v2 but can there be an option to collapse the side bar with all the metadata types? When doing diffs sometimes I wish I could have the full width of the screen.
1 vote -
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 -
Custom Sort Conflict files by metadata type
I would like to be able to sort conflicting files by metadata type in the conflict screen. That way I can resolve conflicts in a more organized fashion.
1 vote -
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 -
Add support to deploy Digital Experiences (LWR) using Digital Experience Bundle Components
Similiarly to how you can deploy metadata for non-LWR Digital Experiences (Aura templates), where you can select different metadata changes individually using Experience Bundle Components, rather than deploying all your changes at once, it would be great if that option is available for Digital Experiences running on LWR (Digital Experience Bundle)
1 vote -
new comparison tool issues
new comparison method/view has a few bugs/bad ideas
when selecting a comparison pair & comparison filter on the "saved comparison pairs" page, the chosen filter does not carry through to the new screen & has to be re-applied
once in the comparison screen, there is no "sele3cted" button like on the legacy page. - this is crucial to know where I'm up to with selecting the parts to release.
2 votes -
Add support for CMS Collections
Please add support for CMS Collections in the comparison filters as well as the deployments and CI jobs.
We're working with CMS Collections in our current developments of a customer community and we'd like to deploy this metadata as well.1 vote -
Vlocity Metadata Types collapse during Compare & Deploy
When you start the Compare & Deploy, for Salesforce Objects, you see all the metadata types broken out as they get completed for 204 types. For Vlocity there are 83 types to select, but when you run the comparison, it collapses to just 1 type of Vlocity. It should show progress similar to hwo the Salesforce Metadata types work
1 vote -
Add the "cloned from" friendly name somewhere on the comparison page.
This suggestion is specific to comparisons that are initiated by cloning a package (that already has been named). Gearset / salesforce takes a bit of time to finish its comparison/validation, so often times I'll open up to 5+ tabs one for each of my gearset deployments. As the comparisons complete, I'll move between the tabs to progress through the steps, but as you can imagine it gets confusing which compare is cloned from which deployment.
Possible ways to display on UI:
When cloning a single package -
e.g.
Apps-87431When multiple packages are combined -
e.g.
Apps-87431
Apps-87431-Step2
Apps-87431-AddFieldUsually,…
1 vote
- Don't see your idea?