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.
1138 results found
-
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.
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 -
Adding Identity Settings to Metadata Deployment
Would be nice, if the Identity Settings can be deployed. Currently, every change on any Identity Settings page has to be done manually in each org.
1 vote -
1 vote
-
Allow us to update the Associated Azure DevOps work item on a successful deployment
Currently within the successful deployment page, you can edit the 'Deployment friendly name' and 'Deployment Notes' which is a very handy feature.
However sometimes we would need to also update the associated work item as the wrong one can be mistakenly associated, this would be a very useful feature for us as a way of correcting such mistakes (that are in fairness rare).
1 vote -
Notify when PR is automatically created (e.g. back propagation)
Notify the developer when a Pull Request is automatically created. For example when next pipeline stage is reached and a PR is automatically created or when a back propagation PR is automatically created.
A comment in related Jira ticket would be very helpful.1 vote -
Allow filtering of records for data deployments via a SOQL
Would like to be able to run a SOQL to select the records to base a data deployment from, in many cases we are trying to build some test data that matches specific scenarios based on fields on parent or related objects.
The current selection of field filters doesn't give us the flexibility we need. For most of our data deployments to sandboxes today we run a data load in prod to set a field to true on the base object from a SOQL and then use that field to filter in the data deployment.
1 vote -
add Dashboard owner to Problem Analysis to use user deploying instead in xml ref
Spring '24 Salesforce added ability to change Owner on a Dashboard https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_dashboards_change_owner.htm&release=248&type=5
"Previously, you had to clone or re-create the dashboard to provide access to a new owner."
This can now cause deployment errors when the Owner is changing between environments if the Uesr does not exist, similar to runningUser user references. Problem Analysis accounts for the latter, but not the Owner. Could we add the Owner scenario to this analysis rule?
1 vote -
apex classes dependencies
When deploying an apex class, check for dependencies. Currently it attempts to deploy even if there are missing fields and only reports missing fields one at a time. Very tedious to address.
1 vote -
Allow disabling of "Caching metadata for faster analysis"
Often this stage of the process seems to take much longer (upwards of an hour) than retreiving and analysing did in the first place.
It's unclear where this is even being cached, i've been told its in my own browser but this cant be true for a CI job with no browser available.
1 vote -
To have an option to run unit tests either for Validation or Deployment or both
Hi - for larger projects with 100 plus or more unit tests, deployments do slow down if there are a lot of them during the day and unit tests run twice. Once during validation and once during deployments. Can we have an option where unit tests can be turned on/off for validation and deployment separately?
1 vote -
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 -
Include the ability to tag/mention someone in the Gearset notes when linking a work item to Azure Devops
Currently, you can post notes in Gearset and these show up in the comments of any linked work item in Azure DevOps, which is brilliant!
The only issue is we cannot leverage the mention/tag functionality, including this would further streamline our deployment process and remove a manual step of having to deploy via Gearset and then manually tag a colleague to update them.
1 vote -
1 vote
-
Roll back feature branches all at once
The tool works really well in the UI promoting things forward through the pipeline. You can select one or more feature branches and promote them one at a time or all at once. It would be great if you could do the same thing with roll-backs. This would make things clean simple and alleviate the fear that you accidentally left something out or accidentally roll-back something you didn't mean to
given that the need for roll-back functionality is inherently somewhat urgent, the tedious nature of having to carefully pick through a larger subset of metadata items to roll-back makes it…
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 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 -
Expand integration for our Pipelines to allow us to enable tools like SonarQube and Veracode to run as part of our DevOps process.
We use tools like SonarQube and Veracode within our company to improve our security and code quality. It would be extremely helpful to have integrations with these tools or an open integration we could configure to work with them. Especially if that could be triggered as part of our pipeline process so this interaction is automated.
1 vote -
Implement a Ticketing Feature
Salesforce DevOps Center has a useful feature that allows users to create different Projects that have their own pipelines. Within each Project, you can create Work Items (similar to Issues in Jira). The user can then perform their work in a Salesforce environment and then run a comparison to associate certain changes to respective Work Items.
From there, each Work Item can be promoted through the various environments in the Project pipeline.
This is really helpful when working on numerous tickets/features for a given project, knowing exactly which environment each Work Item is in and the various metadata elements that…
3 votes
- Don't see your idea?