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.
14 results found
-
Add Failure Information to CI Job's Email Notifications
Currently, Unit Test jobs provide a nice email notification of what tests failed right in the email body.
CI jobs, however, provides the same generic message for failures for validations as below:
"The validation only CI job, Release Validation, has failed. Find and fix the validation issues on the error summary page in your CI job history"
and for CI deployments
"A continuous integration job, Prod to Dev3, has failed. No changes were deployed to the target org.
Find and fix the deployment issues on the error summary page in your CI job history. "
It'd be great to get…
1 voteReleased
-
Update CI Job History Exports to include User and DateTime Stamp
In the CI Job section under the view history button, when selecting the ability to export the changes, Is it possible to include a DateTIme stamp
and User column for each row change?10 votes -
Include Test Run Details in Deployment Report for Validated packages
In the Validation deployment flow, there currently isn't a way to view test execution results if they aren't manually exported during the process. Having the ability to view the Validation Deployment report and details in this deployment flow is actually more valuable than the actual deployment report that is generated.
If we can't have that, it would be nice to be able to continue to export those test run results after deployment as part of the deployment details.7 votesYou can now access the outcome of test execution results for validated packages via the ‘View components’ menu item located under the More actions icon.
-
Provide reporting capabilities for Deployment History
Our executive sponsor for Gearset has asked me to provide him with some metrics around our Gearset usage. Specifically, we would like to be able to have access to some of the data that already exists in the Deployment History section, but in a format where we could report on it. Ideally, we'd be able to show how many deployments to production, how many components deployed in those packages, frequency of production deployments in a given timeframe, etc.
This would be a very valuable feature for us so that we can ensure our executive leadership team is briefed on the…4 votesThe deployment history can now be exported as a CSV file that will enable you to create the metrics you’re looking for.
Regards,
The Gearset Team
-
Notify Slack when deployment is successful
I would like to inform Slack on when a manual deployment is successful or failed. It will tell me what the source environment and what was the destination environment. It will also tell me if what the success/fail ratio of the tests that were run.
30 votesYou can ask Gearset to post to Slack or MS Teams when a manual deployment succeeds or fails to all or specific connections (including orgs and Git). See more:
-
Allow scheduled jobs to be assigned a different authentication user
We would like the ability to change over scheduled monitoring/testing jobs to a different authentication user. Currently if we need to switch an authentication we lose the history.
Consider:
I leave my employer and I need to switch the monitoring over to another developer or admin. I have to delete all the current scheduled jobs and re-create them using the other users authorization. Which causes the history to be lost.11 votesThe feature was completed. The documentation is at https://docs.gearset.com/en/articles/3758806-transferring-ci-job-ownership
-
Specify friendly name before deployment
We would like to be able to specify the desired friendly name before a deployment completes, maybe above notes on the summary screen. The friendly name is copied from an existing draft, but when we clone from sandbox to sandbox and finally prod, there's no need to save a draft every time. Ideally, the friendly name would default to that of a cloned deployment as well.
4 votesThe ability to name the deployment from the pre-Deployment screen is now available, and will be used as the friendly name.
-
Add the Deployment Friendly name to the Deployment Report
On the deployment report pdf can we add the deployment friendly name above the deployment notes.
3 votesThis has been completed and friendly names will now appear on the deployment report.
As always, feedback welcome!
-
Show a browser alert after a long running operation
Some operations, such as a comparison or deployment, can take some time. I normally navigate to another tab. It would be good to get a browser alert when the operation is finished and I'm needed again
1 voteThis has now been completed
-
Allow selecting a metadata comparison filter when editing a existing job
For monitoring / backup and CI jobs, when looking at the Metadata Filter tab, it would be great to be able to select from the Metadata Comparison Filter. Sometimes I want to be able to reapply a custom filter.
Specific example - I have a monitoring / backup job. Originally it was comparing 65 metadata items. Later, I changed the filter to compare all 96 types of metadata. Now, I want to undo my change. How do I get back to the original 65 without manually unchecking each type?
Thanks!
2 votes -
Provide link to the deployment status
When CI Jobs are running or when monitoring a deployment, it would be nice to have a link to the target salesforce environment's deployment status page.
2 votesThis work has now been completed, so a link is shown on the `Deployment in progress…` page that will take you directly to the deployment status within the target Salesforce org.
Thanks,
Kevin -
Display deployment history in a list
Currently viewing the deployment history requires opening a pdf. If going back in time the only way to find a specific item that was deployed is to open one pdf at a time and look for the change.
It would be great if clicking on a past deploy would show items deployed in a list form on the page itself. This would make finding a past change easier.
2 votes -
Object level filters for Monitoring
Object level filters for Monitoring
1 vote -
Show which tests have been run
In the post-deployment summary, rather than just list the numbers, list the actual tests that have run.
2 votes
- Don't see your idea?