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.
1289 results found
-
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.1 vote -
Add an option to ignore API version differences during comparisons
When comparing Apex, and other files with API versions the difference engine will mark any files with higher API version as "changed", even if the API version is the only change. This can be undesirable when there have been bulk updates to the API version that have not been made in the development environments. It would be great if the comparison engine could make it clearer when the only difference between two files is an API version (especially when the target is on a higher API version)
1 vote -
Allow open PRs to queue up.
Allow open PRs to promote via selection and to queue up against the target keeping blocking behaviour to just merges and the deploy activity
1 vote -
Problem Analyzer should remove picklist values from record types when picklist values are removed from the picklist or value set.
When removing or deactivating a picklist value, Problem Analyzer should remove these values from any record types that reference them. While the initial deployment of the picklist may succeed, subsequent deployments of the referencing record types will fail if they still reference a deactivated picklist value.
1 vote -
Picklist Comparison should show if value is active/inactive
When comparing a picklist in which we have deactivated values, the simplified comparison visualization shows the deactivated values as being "added" (in green, on the source side).
The XML reveals <isactive>false</isactive> is being added, but the simplified view seems to suggest new values are added instead
1 vote -
New, one-click "Promote" button is very risky
In Deployment Pipelines when a PR for a CI Job is selected, a new, one-click "Promote" button exists, if the PR passes merge-conflict and validation checks. This new button is very risky in that it begins the promotion process, without recourse, when clicked.
Perhaps that's the designers intent but for myself at least, the button is too easy to accidentally click out of inattention, distraction or mouse clumsiness and is especially risky in that I cannot recall the action.
Personally I like the process of clicking the PR checkbox and clicking "Promote", which prevents unintended deployments.
As an alternative to…
1 vote -
audit report missing PR message
The audit reports don't include much context of the deployment, which means they are pretty useless to us and do not serve our auditors' needs. Specifically, they do not include the PR message for deployments through our pipeline, which means we can't link each deployment to the specific ticket responsible for that deployment. The PR message is where we put our ticket. This information is needed for our SOX audit process. Additionally, we can not see a link back to the deployment, which would allow us to quickly reference the specific metadata files/components that were deployed.
1 vote -
Pre-fill Pull Request Description with comments from last commits
In order to save time, when a Pull Request is created from the Pipeline, the Description field could be pre-filled with the comments from the last commits in the feature branch, instead of forcing the User to type something.
1 vote -
Use location of metadata in source branch or local folder when adding to target branch
When adding a file from a branch or local folder (source) to another branch (target) not having the file, use its location in the source as the location in the target.
Currently all new files are placed in the default folder [1].
Let's assume a new file, "HelloWorld.cls", in the source is located in .../force-app/main/default/classes/special/ and that class doesn't exist in the target. When the deployment is complete the file should exist in the target's .../force-app/main/default/classes/special/ folder, matching its location in the source. Currently it would be placed in .../force-app/main/default/classes/.
[1] https://docs.gearset.com/en/articles/2835001-structuring-your-source-control-repository
1 vote -
Save sort order of grids
It would be nice to be able to sort by column names and save that sort order for the next time the page loads or save a default sort order. We sort often by jobname and would like to not have to resort everytime we need to touch a ci job to sort the column.
1 vote -
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 -
is it possible to add a filter for "selected feature branches only" ?
is it possible to add a filter for "selected feature branches only" ? My business problem is that i am a deployment manager and i need to quickly validate what ive selected before building the release.
1 vote -
Is it possible to get an additional field in the compact view of the jira ticket ?
Is it possible to get an additional field in the compact view of the Jira ticket ? We would like to add Fix Version as well as what already exists.
1 vote -
Show Date/Time of Validation Run in Validation Details
I would like to see the "Effective Date" of a validation in the Validation Details screen (at /continuous-integration-job-validation-errors).
I only ever access this information from the Deployment pipelines and so don't ever see the date/time the validation was run (near as I can tell this is only available in the CI jobs section).
To better explain my reason for asking:
Oftentimes when a validation fails it is sufficient to rerun the validation (on account of Delta CI jobs doing weird things sometimes). What I've found myself doing is perusing the validation errors, clicking "retry validation", then going about other tasks…1 vote -
Visibility to Log Files for Connections and Compare & Deploy Events
When you either make connections to 3rd party applications or run a Compare & Deploy, there is no visibility to the log files, I feel these should be accessible to the user so that we can understand the reason why something is failing and not have to have someone provide this information. Additionally it should have options to change the level of logging to provide detailed information when needed
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 -
Filter metadata types based on whether org is licensed for that metadata or user permissions for that metadata
Compare 2.0 Metadata types
Why am I seeing Fuel Type and Fuel Type Sustainability Unit of Measure ? Running user needs a special permission set to see these metadata types and I, as running user in Gearset, don’t have this permission set.
This is an example of a general suggestion wherein if the source org/running user isn’t licensed/permissioned for some SFDC metadata, it shouldn’t appear in the (lengthy) enumeration of metadata types
Other examples are Live Chat XXX, PaymentGatewayProvider, SchedulingXXX,SustainabilityUom,SustnUomConversion, WebStoreXXX and many more
1 vote -
User Data & Logs
For audit reason we have been asked to provide a comprehensive user list with the following data:
User Status (Active/Inactive)
User Creation/Removal Date
Created/Removed/Updated by
Updated Value (if you change the role of a user from member to owner or opposite)
User Last Login DateThese data are part of the user audit control (create/update/remove users) and are very important to prove you have control who gets access, and there is no risk for unauthorized access but also to prove that segregation of duties is in place.
Thank you!
1 vote -
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
- Don't see your idea?