Umbraco

Severity Levels

We operate with a number of severity levels. Below you’ll find a description of the severity levels as well as definitions and examples hereof:

 

Severity 1 (highest)

  • Umbraco CMS security defect affecting site integrity and/or access to the publishing/editing API, with evidence of exploitation or public knowledge of the issue. 
  • Umbraco CMS regression* causing non-availability to site/publishing.
  • Umbraco Deploy regression preventing publishing of time-critical content without a workaround.

 

Severity 2

  • Umbraco CMS security defect not affecting site integrity but vulnerability, with evidence of exploitation or public knowledge of the issue. 
  • Umbraco CMS regression causing intermittent site access issues – such as for some users.
  • Umbraco Deploy regression affecting publishing of content.

 

Severity 3

  • Umbraco Deploy security issues, with evidence of exploitation or public knowledge of the issue. 

 

Severity 4

  • Usage - such as UX, plug-in behavior, and other UI quirks.
  • Umbraco CMS regression causing performance issues related to the Umbraco CMS code base.
  • Umbraco Deploy performance or usage issues.

 

Severity 5

  • Ordinary support questions not related to any operational matter.
  • Request for code review and/or architectural advising.

 

The severity level is decided upon based on mutual agreement.

 

Definitions

* A regression is defined as a feature previously working on the same major-version.