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.
237 results found
-
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 -
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
3 votes -
1 vote
-
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 -
Permission set changes not displaying without drilling down
You shouldn't have to drill in to see the changes in a permission set. I was stumped b/c it showed no difference, but in reality I had to drill down to see the difference. This is bad UI
2 votes -
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 -
Show Metadata API version used to retrieve metadata for comparison on comparison result page
It would save time and give confidence if the specific Metadata API version number used to retrieve the metadata was displayed on the comparison results page.
2 votes -
Precision Deployments (available for Layouts) for all the meta data
Precision Deployments for Layout is a great improvement, it would be great to have the same feature for other meta data, particularely for : Fields picklists, global value sets, List Views, Reports, Profiles, Permission Sets and why not Lightning Pages, now that the Dynamic Form is available for Acc, Contacts & Opp
19 votesAll - please let us known in the comments which metadata types you would like us to support next with precision deployments. Thanks
-
exclude specific JSON keys when comparing Vlocity/Omnistudio metadata
We are seeing Omniscripts showing as different on certain JSON keys. These keys always change and should be excluded from your comparison.
The impact of this is Omniscript deployments require the LWCs to be compiled and if we deploy Omniscripts unintentionally, their LWCs are not recompiled and functionality breaks for the users.1 vote -
Deploy Now and Validate Package Buttons
Presently, the Deploy Now and Validate Package buttons are positioned adjacent to each other. Occasionally, there is a risk of unintentionally selecting the Deploy Now button before the package has been validated. This can result in potential issues arising. To address this, I recommend the following actions:
- Enable the Deploy Now button only after the Validate Package process is successfully completed.
- Consider repositioning the buttons within the User Interface if both buttons share the same screen.
- Alternatively, place the Deploy Now button after the Validate Package screen in the sequence.
Thanks.
1 vote -
Deploy Managed Custom Filters Globally
When we associate a custom filter with a particular CI job, and then make changes to the filter, give the user the option to push those changes to all jobs (list them out) that use that named filter.
4 votes -
Allow download of XML files from the comparisons page
In some instances, we have to use the Metadata API to download XML files for analysis. However, the Metadata API is a pain to use. Even Salesforce recognizes this and suggests using a migration tool like Gearset to extract these: https://developer.salesforce.com/docs/atlas.en-us.246.0.api_meta.meta/api_meta/file_based.htm
Since Gearset retrieves these files during comparison, it would be great if there was an option to download them to a zip file directly.
Note: There is already a "Download Package" feature on the deployment page. However, we obviously can't add items to this page if there is no change between the orgs. So, if a similar feature were…
1 vote
- Don't see your idea?