How does Uplevel classify Issues?

Overview

Uplevel’s ML Issue Classification model provides key visibility into engineering effort and time spent on New Feature Development vs. Defects vs. Sustenance without dependencies on how teams are tagging work.

How it works

The Uplevel Machine Learning (ML) Issue Classifier uses issue metadata from standard fields like Issue Type, Summary, Description, and Assignee, as well as similar Epic metadata if the issue is linked. From there, an issue is classified as one of three categories:

Details

****💡Example: A task titled "BE: verify issue handling and NPE logic" has been flagged as Sustenance, but with low confidence it is only slightly favored to be sustenance compared to a defect. In this case, Uplevel would put it into "Uncertain Classification" by default.

Accuracy / Results

Uplevel has seen great success in the accuracy of our ML Issue Classification model with current customers to-date. We’ve directly compared our ML Issue Classification models to custom aggregations and manually tagged categories already leveraged by Uplevel customers today, which has provided the following results:

  1. The current model for defect vs not defect:
  2. The current model for new value creation vs sustenance:

FAQ