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.
1233 results found
-
Please add support for decomposeCustomLabelsBeta
Salesforce added the option to configure multiple features in the DX Project Configuration file. One of the is breaking down the big CustomLabels file into individual files where we no longer need to deploy the whole file but just a file (label) that has changes in. Please see SFDX Documentation here - https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm
10 votes -
Provide the ability to get a deployment report on multiple deployment packages
Instead of having to download the deployment report individually for multiple deployments, I would like to be able to select multiple deployments and download one report that contains a list of all files that were deployed as part of the multiple deployments. It is too cumbersome to manually download a report or .csv for each deployment and then copy/paste the info into one location so that I can get a comprehensive list of all files that were deployed.
8 votes -
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.
13 votes -
Save Problem Analyzer Changes to Deployment Set
When using the Problem Analyzer to identify and fix issues within deployment sets, it's common to add or remove items to address specific problems. Currently, these changes are not automatically saved, which can lead to recurring issues in subsequent analyses.
Suggested Enhancement:
Introduce an option that allows users to save their modifications directly to the existing deployment set or create a copy of the set with these changes. This feature would streamline the problem-solving process and ensure that resolved issues do not reappear in future analyses.Benefits:
Efficiency: Reduce the time spent on re-analyzing and re-fixing recurring issues.
Consistency: Ensure…4 votes -
Option to create a CI job only for back propagation
We created some CI jobs for back propagation of changes from Production to other downstream branches and orgs. But these CI jobs also pick up pull requests(from a different pipeline) for forward propagation.
So, basically there is no way currently to create a CI job just for back propagation. It will be good to have a toggle in the CI job to mark it for forward or backward propagation8 votes -
Add the ability to set Metadata filters for all Pipeline environments at once
In order to update the metadata filters in a pipeline, one must individually update each environment's metadata filter from the list of Continuous Integration jobs.
It would be amazing to be able to set a metadata filter in the pipeline and have it propagate to all environments in the pipeline.
12 votes -
Add the ability to put CI jobs into folders
It would be great if we had the ability to put ci jobs into folders. We've accumulated a number of CI jobs. Some of these jobs are no longer in service and we're a bit reluctant to delete them as they may have historical information that we may later want or need. It would be great to be able to put things like this into folders to help reduce clutter and organize our CI jobs page. thanks for your consideration.
3 votes -
documentation
I have been really impressed by the visualizations on the Compare and Deploy interface. Particularly the lightning page layouts and flows. One of my most time consuming tasks is creating internal documentation and I have not found a tool that allows me to capture the level of detail that I want in an efficient way. It would be great if I could export the visualizations at the bottom of the compare and deploy screen. It would be even better if it could export directly to Confluence.
2 votes -
CI jobs view improvements
Hi Team,
when opening a CI job and then expanding them, I can see a list of PRs with status 'Succeded' for two days I thought those were the successful deployments. Technical support confirmed instead that those are the PRs where the Validation Job has succeded but not yet deployed. The view is a bit confusing because for validation jobs I would expected a status = 'Passed'.
Also, when I open the 'View History' of the actual deployment job it takes me to a view where I can see the github ID but not the PR number/name. It would be…2 votes -
Offer Japan data residency
We are headquartered in Japan. Japan has data residency requirements for data backups/deployments and even metadata deployments/processing.
Please add the option for a Japan hosted Gearset account.
2 votes -
Assigning a dev sandbox to a member should give them deployment access
Assigning a dev sandbox to a member should give them deployment access automatically, or at the very least I should be able to give deployment access in the same interface.
2 votes -
Quick deploy in pipelines
It would nice to be able to use the Quick Deploy feature once a release is validated, instead of either hitting deploy or scheduling the deploy and having it validate one again.
21 votes -
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 -
Check for maximum flow versions reached as part of the pre deployment error check
The problem analysis does not detect that the deployment will fail due to max number of flow versions
1 vote -
4 votes
-
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 -
jira comment after deployment
Right now gearset posts comments to Jira when validation is completed and PR is merged.
We would like to have comments also when deployment is completed.The current comment "Successfully merged PR #297 from gs-pipeline/SF-23601-preprod into preprod" tells nothing to business users, they are not aware of git, CI/CD and what this message means.
Comment "Deployment to preprod is completed" makes much more sense for them.2 votes -
Add Salesforce Data Cloud sandboxes as an option for deployments
Salesforce Data Cloud sandboxes are now generally available but to promote changes from sandbox to production, the only options are through Data Kit and change sets, CLI, or DevOps Center. Having the option to use GearSet would be helpful so all deployments were managed the same.
1 vote
- Don't see your idea?