Sys Admin Issue Severity

When creating an issue related to ofn-install or other sys admin, you need to set up a severity level so that the issue can be prioritized. The issue can be either related to operation of a platform e.g. emails not working or related to ofn-install and how ofn is deployed. Affecting users can mean affecting end users OR affecting dev / sys admin.

Note: a triage session is done each week by XX(?) to confirm severity level and add any severity 1s and 2s to the train for action.

Severity 1 🔥 🔥 🔥

Description: this issue is stopping someone's instance from deploying or 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

Once you have created this issue, please post in Slack #deployment calling for immediate help

Examples:

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

Severity 2 💣

Description: the issue is affecting any of the non-critical features described in Severity 1 and there is no workaround. Most users are impacted.

Timeframe: as soon as possible

Examples: TBD

Severity 3 😷

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

Timeframe: when you can

Examples: TBD

Severity 4 🤒

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

Timeframe: maybe one day

Examples: TBD

Severity 5 😞

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

Timeframe: not likely ever

Examples: TBD