♨️Issue Priority

Throughout our work, at Vital you will experience several issues that will arise from releases, products, and codes. This document is intended to give you guidance on how we think about prioritising issues and triaging them.

Bug Priority vs Bug Severity

• Priority

  • How important is it to our cycle planning?

  • Would you ignore this bug and continue working on cycle planning?

• Severity -

  • Objective assessment of a bug’s impact to the functionality of the system and to the end user.

We will have three scales - P0, P1, P2

P0 (Blockers)

Resolution: < 1 day

We should stop working on the cycle to fix the bug. This is reserved for serious issues that are high severity and high priority.

Examples

• A customer/Multiple Customers have reported all data is not flowing in for all users for a specific provider

• Webhooks stop working

P1 (Critical)

Resolution: ~ 2/3 days

This is likely affecting a customer but is narrowed to

Examples

• A customer reported missing data specific to 1 user

P2 ( Medium,Low)

Resolution: ~ 5 days

Represent pretty much anything that will only be fixed when our development team has cleared all

Examples

• This is likely affecting a customer but is narrowed to a specific user.

This is inspired by GitLab

Type of Bug	P0	P1	P2
General	Broken feature with no workaround or any data-loss.	Broken feature with an unacceptably complex workaround.	Broken feature with a workaround.
Performance Response time(API/Web/Git)	Above 10,000ms to timing out	Between 4,000ms and 10,000ms	Between 1000ms and 2000ms
UX	"I can't figure this out." Users are blocked and/or likely to make risky errors due to poor usability and are likely to ask for support.	"I can figure out why this is happening, but it's really painful to solve." Users are significantly delayed by the available workaround.	"This still works, but I have to make small changes to my process." Users are self-sufficient in completing the task with the workaround but may be somewhat delayed.
Vulnerability	Any PII or PHI is at risk of being leaked
Tests	Live production tests are broken
Provider	Provider outage is widespread across all customers. Or all customers are missing summary data types .