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.
1465 results found
-
Include "Messages reported by Salesforce" during Metadata Deployment in the final report
During a metadata deployment, on the "deployment in progress" screen, there is a column for "message reported by salesforce".
I think these should be included in the final results screen, and perhaps in the deployment report.
These can be useful for the user to do things like make changes to their flows to conform to salesforce best practices.
2 votes -
When merging a Pull Request that is linked to an Azure DevOps work item, indicate the user who performed the merge
Currently, when a PR is merged into an Org (and the PR is linked to an Azure DevOps item), a discussion comment is added to the DevOps item documenting the merge. However, there is no indication in the comment to document the user who performed the merge. The Author of the comment appears to be the owner of the pipeline, not the user who performed the merge. My suggestion is to either make the author of the comment the person who performed the merge, OR in the content of the comments, add a line to indicate "Merged By: [Name of…
1 vote -
retain validation history for CI jobs
When a pull request is created against a branch that triggers a CI job, a validation is run. Sometimes, this validation hits errors and adjustments need to be made to the metadata filter and/or problem analyzer template until the validation succeeds. However, once the PR is promoted and the CI job successfully fires, the validation history for that PR is no longer accessible. It would be useful to be able to retain that validation history, as it would help to do further investigation into the validation errors that were hit after the fact.
There is not always time during a…
2 votes -
Provide deployment options for Mulesoft via Gearset
As Gearset does Salesforce based deployments so well, it would be great to have Mule deployments done through Gearset as well.
4 votes -
Include Pull Request title in the notification
Hello GS team,
Currently, the notifications from the pull request validations only include the PR number, I would like to request if it's possible to include the PR title.
Current Sample: [Gearset] CI validation job Validation job for PR #11111 failed
With the title in the subject of the notification, we can FW the results to the right teams automatically.
Thank you!
3 votes -
add a column for file sizes and show a warning message if over the limit (might happen deploying content assets)
Recently when deploying a large amount of content assets, I ran into a issue where the deployment would freeze on caching metadata for faster comparison.
Support told me the deployment size was too large and I broke it up into smaller deployments. I suggest adding a column with file sizes and perhaps a warning message if you exceed the deployment limits.
3 votes -
Allow automated unit test execution to run tests synchronously
When unit tests are run in parallel you can often get intermittent errors such as UNABLETOLOCK_ROW. When running tests from Salesforce you are able to specify running tests synchronously which takes longer but prevents conflicts between tests. Can this option be added to Gearset for the automated test running?
1 vote -
Ability to report on runtime in Gearset Reporting API and what metadata filters were used
As part of showing the amount of time saved by using Gearset (and DevOps best practices), as well as the overall current utilization of Gearset across multiple teams and Gearset instances, being able to report on the Comparison, Validation, and Deployment runtime would be extremely beneficial. Also reporting on which metadata filter was used, if named and saved/accessible, in a comparison, validation, and deployment.
This data could also be used to identify inefficiencies in the standard metadata filters used across our Gearset instances, and potentially identify clients not deploying smaller and iteratively in order to prove with data how that…
5 votes -
Flow equivalent of Static Code Analysis-esque rules
Code Analysis rules run against Apex in Gearset. As Salesforce development continues to rely on Flows as the main tool for declarative automation, it's becoming challenging to catch known inefficiencies, known issues, and discouraged usages. It would really set Gearset a part as a deployment tool to utilize issue detection or run "rules" against Flow metadata to call out potential issues or flows not following best practices to even prevent a deployment or commit from occurring.
Examples: SOQL or DML in a loop, the number of elements for flows (prior to api v57) or general overall complexity, lack of Descriptions…
4 votes -
Export and Import Gearset metadata filters to other Gearset instances
This idea feels relevant to Gearset customers that are consultants or in professional services teams.
Our team will be managing multiple instances of Gearset for various clients. During the initial setup and also over the long term maintenance of those instances, it would be ideal to standardize the custom metadata filters being used. The base filters would be the same starting point for all instances, because of the references to namespaces and certain metadata types involved in our projects.
Currently, the filters will need to be part of the post-instance setup steps. It would be ideal to be able to…
3 votes -
Deploy monitor results changes to target org directly from the compare screen
I get the a monitoring results email. When I click it it takes me to the comparison screen
Right now to deploy those changes I have to go to Monitoring > Filter by name > View History > Select the right one > Deploy changes to target org.Those are 5 clicks to get to a place I just was in! It would be great if I could deploy the changes to the target org directly from the screenshot comparing screen.
1 vote -
Recognize code formatting changes as differences that can be deployed
If an Apex Class or other code file has been modified to fix formatting only, changing the indentation size for example, Gearset doesn't recognize this as a change that can be deployed. Formatting changes are recognized by git and SFs own source tracking feature so it should be recognized by Gearset.
2 votes -
quote term
For CPQ Quote Term, the name column only shows "Approved" which is not meaningful.
Please switch to using the "Name" field which is a auto generated number (e.g. QT-0209) that is displayed in the user interface and therefore a meaningful identifier.1 vote -
Add configurable email reminders for scratch org expiration.
From Salesforce orgs and Dev Hubs, it would be great if there were a setting that would automatically send an email when a scratch org is approaching expiration. This could be configurable per Dev Hub, and would help prevent data loss at scratch org expiration.
1 vote -
Ability to export the unit test coverage in the json format and push it to the repository automatically
The sfdx CLI has the ability to generate a report of the unit test coverage in JSON format with the default naming convention test-result-codecoverage.
I would like to be able to retrieve this JSON file and push it automatically to the repository on every unit test execution.
As an example please find a possible sfdx command to achieve it: - sfdx force:apex:test:report --testrunid 7075J00001NZBNIQA5 -c -r json -d folderDirectory #testRunID is the value from the ApexTestResult obj AsyncApexJobId field
Please find more information on the official salesforce documentation about it https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_testing.htm3 votes -
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 -
Save Filtered Metadata from a Comparison View as a New Custom Filter
When running a compare, we'll often filter the list of metadata types in the results to eliminate types we're not interested in comparing. It would be nice to save the filtered view as a new Metadata Filter for use in a future compare.
2 votes -
Show the status of a CI deployment on the pull request
We use merge-based deployments, so whenever a Github pull request gets merged to /main, a CI deployment job fires that deploys the content of the PR to Production.
The issue is that at the moment all Merged PRs look the same, whether the deployment actually succeeded, or failed. There's no way to tell, or even to follow progress, unless we ask people to open the Gearset job and then look at the deployments for that job etc. which is quite a bit of a faff.
Validation jobs do display on the PR whether they passed or failed, the same feature…
1 vote -
Manual button to refresh repository data
Multiple times in the past, my team has added new files to our git repository and Gearset dose not pick them up as existing in the repository when we do a comparison.
Select your git repo/branch as the source, select the sandbox you want as a destination, the comparison page says "fetching repositories", but it doesn't seem to actually pull the updated data from the branches. My comparison builds fail because the new file isn't included in the comparison. Gearset usually ends up picking them up in ~12 hours but it's a huge workflow blocker when a tool doesn't have…2 votes -
Option to download problem analyzer template
Option to download the problem analyzer template so users have an option to add it to the custom github actions scripts to run CI validations for their own delta comparisons.
1 vote
- Don't see your idea?