Bug severity

When reporting a bug, you need to set up a severity level so that the issue can be prioritized in the backlog.

Note: the delivery team review each bug to confirm severity level and add any severity 1s and 2s to the delivery train backlog for action.

Severity 1 🔥 🔥 🔥

Description: the bug is stopping the platform from working, and there is no workaround. Lots of users are impacted and the affected feature is one of the critical ones: checkout, payments, signup, login.

Timeframe: immediately

Examples:

• the application is inaccessible in a given instance
• checkout crashes, not possible to make an order

Severity 2 💣

Description: the bug is affecting any of the non-critical features described in Severity 1 and there is no usable/intuitive enough workaround. A significant number of users are impacted.

Timeframe: as soon as possible

Examples:

• the private shopfront is not working and the workaround is unusable

Severity 3 😷

Description: the bug is stopping a critical or non-critical feature but there is a usable workaround. Some users are impacted.

Timeframe: when you can

Examples:

• The date picker doesn't work but we can change it in the date text

Severity 4 🤒

Description: the bug is annoying, but doesn't prevent from using the platform. Not so many users are impacted.

Timeframe: maybe one day

Examples:

• When copy paste text in shopfront welcome message, annoying white strips appear

Severity 5 😞

Description: we can live with it... Few users are impacted.

Timeframe: not likely ever

Examples:

• Australian staging 1 refers to images of staging 2