Post-release regressions
Post-release regressions: catch what a release broke from the tickets that follow it.
A post-release regression is something that worked before a release and stopped working after it. Customers can report it before anyone on the team notices.
It is not error tracking. The regression analysis does not read your logs or your release feed. It reads what customers write, in their own words.
14 days with every Pro feature. No card.
How it works
Every morning, over the last 3 days.
Post-release regressions, frustration signals and churn signals run every morning over the last 3 days. The regression analysis reads each conversation’s subject and the start of the messages in the thread, and looks for new or worsening problems that point to a recent release.
For each one, it rates the severity, counts the conversations that mention it, and suggests what to do first. When it finds none, it says so.
What you get
A finding you can act on.
Severity
Critical, high, medium or low.
The tickets behind it
How many conversations mention it, and the tickets it cites.
The trend
New, steady or getting worse, by the same rule as support ticket trends.
An investigation brief is written for bugs, regressions and anomalies. It reads up to 8 of the conversations and sets out what customers say goes wrong. Customers are paraphrased; errors are quoted as sent.
When you have reviewed it, file it to GitHub, Linear or Jira.
While you fix it
Replies that know which version the customer is on.
GitHub also lets a draft read your code at the customer’s version, when the ticket or their account says which one. A draft can then say whether a problem a customer reports is already known and still open, and, with GitHub releases, which version a fix shipped in.
When a customer reports a bug in a WordPress plugin or theme you list in Settings, Overdesk can start a private test copy of WordPress with it and try what they describe. The reply says what it checked, or that it was not tested.
Bug and churn findings and customer context are Pro features. See plans and pricing.
Questions
Does the regression analysis know when we ship a release?
No. It reads what customers write, not your release feed. When customers start reporting a problem that points to a recent update, it becomes a finding. If you connect GitHub, drafts can read your code at the customer’s version.
Is this the same as error tracking?
No. Error tracking reads what your software logs. Overdesk reads what your customers say. A regression with no error, like a button in the wrong place or a setting that no longer saves, still shows up in tickets.
What if nothing broke?
It says so. The analysis is asked to say plainly when it finds no new or worsening problem.
Which plans include it?
Post-release regressions run on Pro and during the 14-day trial. They are not on Assist.
Something we didn’t cover? Email us or book a demo.