Bug severity

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

Severity 1

Description: the bug is stopping the platform from working properly, and there is no workaround. Lots of users are impacted. Timeframe: IMMEDIATELY Examples:

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

Severity 2

Description: the bug is stopping critical functions and there is no workaround. Most 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 function 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] (https://github.com/openfoodfoundation/openfoodnetwork/issues/394)