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.
221 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.
6 votes -
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 -
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 -
Configure the "Saved Comparison Pair" to always use a specific Comparison Filter
When managing multiple orgs, and running comparisons, the Saved Comparison Pair saves a lot of time. However, sometimes we need to use different Comparison Filters, based on which environments we are comparing.
Instead of first choosing the Comparison Pair, then manually selecting the Comparison Filter to use, it would be great to be able to (optionally) configure the Comparison Pair to use a specified Comparison Filter.
Example Use Case:
When committing work from our Dev org to BitBucket, we exclude Apex Classes & Triggers, and mainly commit declarative functionality (Apex code is committed separately from our dev team). All development…
4 votes -
Add support for OverrideSettings for Vlocity datapacks
It would be great if there is a way to set up OverrideSettings https://help.salesforce.com/s/articleView?id=sf.os_build_tool_override_datapack_settings.htm&type=5 for the deployment pipeline. For example, FilterFields can be specified, so those fields are removed from the datapack before being committed to the git repo.
This should help to reduce the number of differences in the compare view when e.g. Salesforce IDs are different or empty attributes are added.
2 votes -
Allow XML comparison to be exported
Being able to extract the XML for the change and the target's differences would allow us to analyze and track label/code changes versus just ordering or location changes.
My issue is similar to the "Enhance XML meta data comparison to ignore changes in XML order" and "Export Comparison details all items" and "Allow download of XML files from the comparisons page"
1 vote -
Search with components returned by metadata comparison
Performing a search across the returned components xml would be helpful. In our org we add a JIRA ticket reference to the Description - having the ability to search for the ticket number string would help narrow the list.
1 vote -
Ability to move existing field to be under another section on layout
If I have multiple sections on my layout.
I have a specific field under one layout section, but now I changed the layout so the field no is moved to another section.
Now I can't do that because the compare and deploy forces me to override the existing section where the field is under.
My intention is to move the field place to be under another section and not delete the other layout section1 vote -
Add exclusion filters for Pipelines
Currently, the metadata filters in pipeline (CI) jobs are either all of a type of metadata, or a defined subset. There is no option to include all, except for a couple of objects, which is oftentimes required.
Please consider adding a negative (exclusion) filter for CI jobs, in addition to the existing positive (inclusion) filters.1 vote -
Include DataWeaveResource in comparisons and deployments
DataWeaveResource has been around for a few releases and is deployable via the Metadata API, but is not supported by Gearset yet. Please include this.
1 vote -
Persist Selection to Include/Exclude Managed Packages in Compare 2.0
When using the new compare, the default is to exclude managed packages. However, we'd like to always include them, so it would be nice to persist the selection from one compare to the next.
1 vote -
1 vote
-
default repository
Allow to set a default repository when you have multiple repositories.
- Navigate to Compate and Deploy
- Select Source Control and select a VCS(in our case Gitlab Self Managed)
- If you have dozens of repositories they all show up on the list
- Need ability to specific a default repo which will be auto selected
2 votes -
Show Created by and Created Date in Comparison view
I'd like to see created by and created date in the comparison view. Sometimes we have multiple users working on items and I may not be the last to modify something but I am the one to deploy it and if I am the creator, I know what it is named but it makes it hard to sift down if I can only show modified by and modified date.
2 votes -
Add to Flow Navigator the flow version description
It would be very handy if the new Flow Navigator view was able to display flow version description. We update this frequently to describe new changes, so being able to read this documentation in the Flow Navigator would be helpful to understanding the flow.
Adding this either as a banner along the top (like some flow xml views) or as an element in the navigator sidebar would be acceptable.1 vote -
Comparison of draft deployments
Two teams who are supposed to be working on different parts of the sandbox org have created two draft deployments. I would like to compare these draft deployments to see if there is any overlap of selected items.
1 vote -
Multiple sort columns for comparison results
It would be helpful to be able to sort comparison results on multiple columns (e.g. first by Metadata type, then by Name). Currently it seems that the results can only be sorted by one column at a time.
1 vote -
Add a date filtering mechanism on comparisons
. Currently we can select individual dates on the dropdown list or select from a select few "Last X days". Would be a great option to be able to set something like "See changes from X to Y" or "Select since X", especially useful given we have the dropdown selection on a per minute step, so the list gets very large, very quikcly.
For compliance checking, tracking who changes what when, periods of criticality (especially around new features coming in) or just for retrospectives.
1 vote -
Allow users to select custom fields even if the object does not exist in the target
Would be great if GS allowed to select custom fields when doing a comparison even if the object does not exist in the target. If I am pushing changes to a repository I might want to only include the fields I created/modified and not the whole object.
15 votes -
Add the package Name to the page, when the package is Opened
Currently when you Open a package like a draft deployment, the Name of the package does not appear. There is a message in top L-H 'Comparison finished' which is not very useful. Perhaps the package Name could go here. It will reduce confusion as you will be able to tell which package you have open. Thanks.
2 votes
- Don't see your idea?