Simple Docs
  • What is Simple?
    • 📕Background
    • 📱Simple app features
    • 🖥️Dashboard features
    • 👩‍⚕️Who uses Simple?
    • 🏥Clinic workflows
  • Try it out
  • Training materials
  • Contact
    • Contact us
    • Customer support
      • Bug priority definitions
  • Reports
    • What we report
    • Building custom reports
  • Engineering
    • Data dictionary & API
    • Android
      • Conventions
      • Deploying to Play Store
      • Bitrise Workflow Quirks
      • Headers sent from the app
    • Backend
      • Audit logs
      • Major flows
    • Localization
      • Android
      • Server
      • Adding/Editing translations for a project
      • Reviewing a translation
    • Technical Hiring Process
  • Design
    • Design
    • User testing
      • Key moments in the user journey
      • User tests
      • Conducting user tests
  • Onboarding
    • Code of conduct
    • Acronyms
    • Glossary
    • Recommended reading
    • Digital principles
  • Elsewhere
    • Simple.org
    • Source code (GitHub)
Powered by GitBook
On this page
  • p0 bug
  • p1 bug
  • p2 bug
  • p3 bug

Was this helpful?

Export as PDF
  1. Contact
  2. Customer support

Bug priority definitions

We mark priorities using these labels on Github and Clubhouse.

p0 bug

Ideal time to deploy fix: within 24 hours

  • App is crashing / none of the users can use the app (e.g.: enroll a new patient, or record a patient's blood pressure)

  • Loss of data anywhere in the system

  • Fix immediately, all hands on deck!

p1 bug

Ideal time to deploy fix: within 48 hours

  • Some nurses are facing severe issues with the app

  • Nurses can't use other features of the app (e.g.: view the Progress tab)

  • Admins cannot use the dashboard

  • Incorrect data being displayed in reports (in the app or on the dashboard)

  • Fix urgently!

p2 bug

Ideal time to deploy fix: within 2 weeks

  • Bug makes app or Dashboard difficult to use

  • Bug may cause errors in analysis in the Dashboard

  • Will likely annoy a large group of users

  • Fix quickly, but not urgent

p3 bug

Ideal time to deploy fix: within 2 months

  • Bug does not affect regular use

  • Bug is more of an annoyance than a critical issue

  • Bug is a polish issue

PreviousCustomer supportNextWhat we report

Last updated 4 years ago

Was this helpful?