YakShaver.ai Blog

Across five releases published from 7 to 19 October, YakShaver improved how generated work fits your project, added a Zendesk destination, and made portal management clearer. This update covers product changes included in releases published between 1 and 22 October 2026, Australia/Brisbane.

YakShaver Anywhere now uses Azure DevOps work item fields and GitHub issue templates when preparing generated work. It can place details such as acceptance criteria into the destination's supported fields, and resolve supported @mentions against project or tenant users. For example, a GitHub issue can follow its repository's bug template, while an Azure DevOps item can use the project's acceptance-criteria field. Fields that a destination does not support can fall back to the description.

The v0.96.0 release adds Zendesk as a destination for YakShaver Anywhere. A project can route a generated ticket to a Zendesk group, include recording context, and set ticket type, priority and supported account-specific dropdown fields.

You can rename project links and widgets in place, see clearer navigation and filter state, and get more reliable recording playback. Shave records also show where they came from, such as a link or widget. These are targeted portal improvements, making it easier to manage a project and understand the source of a report.

Project admins can see and sort widget counts, filter the Projects list to projects with YakShaver Widgets, and jump to widget setup. This view is for project admins.

YakShaver Anywhere added silence and speech detection to filter transcript segments that do not contain speech. This helps keep words generated from silence or sounds such as ringtones out of a work item. The 19 October release also extends speech filtering to recordings processed through Teams, OneDrive and the browser extension.

A recorder fix also prevents a screen-share recording that contains audio from being incorrectly labelled “This recording has no audio”.

• v0.95.4 — 7 October: Portal improvements and transcription filtering.
• v0.96.0 — 19 October: Structured work items, Zendesk, widget administration, attribution and recording fixes.
• v0.96.1, v0.96.2 and v0.96.3 — 19 October: Maintenance releases.

Want to try YakShaver? Visit yakshaver.ai or open the demo.

See you for your next shave. 🐂

Over the last month, the YakShaver team shipped 15 new releases. The biggest changes make it easier to send a report, share a YakShaver Anywhere link, and see what's happening while a report is recorded or processed.

YakShaver Anywhere can now send a work item to an email address, alongside its existing destinations. Setting up a GitHub project is easier too: if the connected GitHub app can access a repository, you can find it in a searchable list instead of pasting its URL.

Create a project link or QR code and share it with reporters. They can open it on a phone and record a shave with their camera, or upload a video from their device.

The link page is now available in Chinese.

The browser recorder warns people when a recording has no audio and shows an error if processing fails, rather than a false success message.

On iOS, the embed widget offers video upload when the browser can't record the screen directly.

Reports keep processing if someone closes the tab. If their live connection drops, the page explains that the report is still underway, helping avoid a duplicate submission. The status page also tells reporters where to look for the result.

The Integrations page is easier to scan on an iPad. Connection status is more accurate, project links are easier to read, and reporters can add a GitHub handle so issues can mention them.

• v0.95.3 — 24 September: Maintenance release.
• v0.95.2 — 24 September: Maintenance release.
• v0.95.1 — 22 September: Added Chinese-language support to YakShaver Anywhere links.
• v0.95.0 — 21 September: Added iOS video upload to the widget and improved embeds.
• v0.94.5 — 17 September: Maintenance release.
• v0.94.4 — 17 September: GitHub issues can mention reporters who add their GitHub handle.
• v0.94.3 — 17 September: Clearer report status, reporter attribution and interrupted-processing messages.
• v0.94.2 — 16 September: Clearer feedback when a live connection drops, plus a fix for recording preview playback.
• v0.94.1 — 16 September: Reports keep processing if the reporter closes the browser tab.
• v0.94.0 — 14 September: Added YakShaver Anywhere links and QR-code reporting, with retry and navigation fixes.
• v0.93.0 — 10 September: Improved the Integrations page, connection status and recording warnings.
• v0.92.0 — 7 September: Added a searchable GitHub repository picker, clearer project links, and recording audio and status fixes.
• v0.91.1 — 1 September: Fixed a blank screen when starting a browser report from the dashboard.
• v0.91.0 — 31 August: Email became an end-to-end work-item destination.
• v0.90.1 — 26 August: Email reporting updates.

Want to try YakShaver? Visit yakshaver.ai, open the demo, or follow @yakshaverai.bsky.social on Bluesky.

See you for your next shave. 🐂

On Wednesday 6 August, between 11:00am and approx. 2:45pm AEST, YakShaver sent repeated Microsoft Teams messages "Video Process Failed" to some YakShaver users. We apologize for both the disruption and the volume of unnecessary messages. The YakShaver users that received the messages, previously has used OneDrive during that outage period.

An internal credential that YakShaver uses to connect to Microsoft 365 expired. On its own, this would have caused a brief interruption to video processing. However, our error handling sent a separate failure notification for every processing attempt rather than a single alert, which turned a routine fault into repeated Teams messages.

When reports came in, YakShaver engineers immediately engaged SSW SysAdmins and together made a plan of attack. They took the affected services offline within minutes to stop the messages, replaced the credentials, and restored full service by 5:30pm AEST the same day. The platform has operated normally since.

The fault prevented YakShaver's platform from connecting to Microsoft 365; at no point was your data accessed or lost. Your recordings remain in your own Microsoft 365 tenant.

Recordings made during the outage were processed automatically once service was restored. If a shave from Wednesday afternoon has not produced a work item, it can be re-run from the portal, or contact us and we will resolve it for you.

We have made 2 changes so this can't happen again.

• Credential renewal has been automated, so an expiry cannot go unnoticed.
• Error notifications are now rate-limited, so that a platform fault can only ever generate a single alert rather than a stream of them.

We apologize again for the disruption.

If you have any questions, please contact us through yakshaver.ai/docs/support

Kind regards,

YakShaver Team