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.
113 results found
-
Allow customization options for the Deployment Report file name
It would be nice to either have the option to set a default file name or allow the ability to set the report file name in the deployment screen.
For my organization, this would make sorting deployment reports for various projects much easier as the file name doesn't include the Package Label.
2 votes -
Expand Permission reporting on the Monitoring job
Expand Permission reporting on the Monitoring job to include Delete permissions reporting on Objects.
2 votes -
Unsubscribe from commit emails
Choose to unsubscribe / subscribe from commit emails (success and or failures) in gearset setup in order to avoid generating unwanted emails (and their PDFs) for each deployment (and save a little CO2 along the way).
2 votes -
Automatic analysis for metadata
Adopt automatic validation for API names of custom objects, custom fields, custom settings, and custom metadata types. Additionally, ensure that the "Description" field is populated to enforce documentation by administrators and developers on Salesforce metadata, including custom fields, custom objects, automation (Approval Processes, Flows, Entitlement Processes), and other applicable metadata types.
2 votes -
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.
2 votes -
Delta comparison between two unit test reports
Hi team. Would be good to have a feature that allows us the comparison between two unit test results. We are interested to export the delta errors from one day to another.
Use case: We are executing deployments for more than 50 pull requests against the same target sandbox, hence regression errors might be introduced throughout the day. We are running nightly unit test jobs and usually, in the morning, we have extra tests which are failing comparing with the previous day.
We are currently exporting the gearset errors from 2 reports, in Excel tables, and compare these ones to…
2 votes -
Export Deployment History Additional Information
It would be great if the Deployment History was able to provide details from Source Control. Specifically, list of people who approved tickets, branch names, commit IDs, etc.
2 votes -
Flexible Org Monitoring Notification Scheduling
I'd love to schedule a weekly or bi-monthly digest email rather than receiving emails for each run or each change. There are developers who need to know when changes are made, but they do not need to monitor changes frequently. In those scenarios, it would be nice to schedule out a weekly review of all changes.
2 votes -
Add Time Column to the CI Deployment page
Due to recent latency issues regarding SF performance issues, I would like to quickly see how long each CI job takes without having to download an individual report for each job. This can either be solved by either:
Adding a field to the CI Deployment page so that I can compare each CI job
Allow me to extract a complete report of all of the CI jobs and open it in excel with the time column so that I can compare the values. I can currently do this from the Deployment history page, however this does not include the CI…
2 votes -
change monitoring for scratch orgs
The Change Monitoring feature only supports normal orgs (sandbox, developer, prod). It does not support scratch orgs
For use cases where developers inadvertently let their scratch org expire with pending, uncommitted work, it would be nice to recover the work before and after the scratch org expires
2 votes -
Filter users for monitoring notifications
Hey,
Would be very beneficial if in monitoring tab, we could filter out users that we get the notifications about.
For example, we don't want to receive changes that changes have been made in a Salesforce org if these changes are a deployment, but we would be interested to see if any users with Setup permissions are making changes to fields, objects etc.
2 votes -
Add tool to send emails after deploying to specific targets
A project manager on my team expressed desire to receive reports when someone deploys to our production org. I would appreciate a tool that sends these emails only upon successful deployment to that specific org so that recipient's inbox is not flooded with every successful and failed deployment to every org.
2 votes -
Restrict visibility for monitoring jobs
I would like to be able to monitor daily changes made without those monitoring jobs being visible to the entire team. We have some super motivated people as well as the other end of that spectrum. I would like to have some data to visualize daily without the entire team seeing what I am doing.
2 votes -
Add a filter in monitoring job to exclude changes done by Gearset
To help identify changes done manually to the org it would be nice to have a filter which excludes all the changes done by Gearset deployment.
2 votes -
Add Salesforce ID to Export History button
Can you add the Salesforce ID to the Export History button for reconciliation purpose.
We currently have to manually match the Salesforce ID in Gearset with the Salesforce ID on the Salesforce Deployment Status page to get the reference between the source ticket in Jira and the deployed change for compliance purpose which is a time consuming process.2 votes -
Send different deployment notifications based on the target org type
Successful deployment notification is for all sandboxes. It would be nice if we can have a separate notification for production and sandboxes as certain people only care what goes to production. Thank you!
2 votes -
Distinguish between process builder and flow
If you do deployments of flows and processes from process builder, both of them are handeled as a flow. If you need to activate the flow or process manually in a production org, you need to guess if it was a flow that you have deployed or a process.
Please within the deployment report (and the comparism), distinguish between flows and processes.2 votes -
Export test run history
Exporting the Test run history to Excel/CSV will allow keeping trends.
The ultimate goal is to include this in a dashboards. If an embedable web page could be generated with solely the trends, that would be perfect.
2 votes -
Be able to start immediately a JOB (CI/Unit Tests/Monitoring)
Add a button to start it immediately. Currently only solution is to change the executing time!
2 votes -
test Monitoring overview - show "is running" + stats
On the Test Monitoring Overview page; you should be able to see at a glance whether the test is running and how many methods have run vs total
Reason this comes up is if you establish a Unit Test run for your developer sandbox org, then you can't run (some) tests from your IDE against the same org "ALREADYINPROCESS Test already enqueued"
A quick glance at the Test Monitoring Overview would tell you if you need to wait 1 minute vs 20 - and guide your activities accordingly
2 votes
- Don't see your idea?