Skip to content
Quality tracker
  • Pages
    • Introduction
    • Prioritization guidelines and Triage process
    • Report an issue
    • My Bugs
      • Submitted by me
      • Assigned to me
      • Grab bugs from your team
    • Triage bugs
      • Acknowledge Bugs
    • Browse Current Bugs
    • Team Dashboard
    • Company Dashboard
      • Trends
      • Release Blockers
    • Notifications
    • Database
      • Bugs
        • Open Bugs
      • Lookup tables
      • Teams
      • Timeline data
      • Forms
      • Metrics Definition
    • icon picker
      Setup
Quality tracker
/
Setup
Share
Explore

Setup

1. Setup your prioritization and other lookup tables


Set Priorities and SLO
Priority
Criteria
SLO
Timeline
P0
Critical business contract agreements are violated (such as SLAs, RTO, RPO, etc)
Core business features are completely broken for all users and/or select critical impact users
Core business feature breakage that is blocking big marketing pushes/launches
Security defects involving
known attacks that impacts the availability or confidentially of customer data or compromise of our platform
accidental leakage of information or accidental leakage of customer data.
Immediate response, even after hours. Fix ASAP. If multiple days of work, update every day.
These bugs are release blockers
If these bugs are already in Prod, their fix warrants an emergency hotfix push
Immediate
P1
Core business features are significantly impacted
Core business features are degrading and might soon impact all users and/or select critical impact users
Core business features are degraded for a significant number of users
Security defects that can potentially
impact the availability of our entire service (DoS vulnerabilities)
disclose user data to unauthorized users (Information Disclosure across users/tenants)
compromise our service (Elevation of Privilege)
Should be investigated and mitigated within 1 week
If these bugs are already in Prod, they might not warrant an emergency hotfix but the fix should go into the next available release
1 week
P2
Business features are impacted but not hindered for a large number of users
Get it fixed within 6 weeks but not interrupting current work
6 weeks
P3
Functionality issues that are not working as intended (such as cosmetic errors)
We seriously aim to get it fixed within 6 months.
OR
This is a real bug but we will not be able to prioritize it. Immediately mark as Will not Fix (Closed) during triage
6 months
There are no rows in this table
⁠
Statuses
Index
Status
Description
Closes Bug
Is untriaged
1
Unacknowledged & Untriaged
New bug, have not been acknowledged (or triaged) by team yet. Bugs get acknowledged within 24h to identify issues that cannot wait until triage.
2
Untriaged
New bug, the team acknowledged the bug belongs to them and is not a P0 but not yet fully triaged
4
Not Started
This Bug has been triaged by the team responsible for fixing it, and it is assigned to an engineer. But the work on fixing it has not yet started
5
In Progress
The engineer assigned has started to work on fixing the bug.
6
PR Merged (Code Complete)
The code for fixing the bug is complete and the last PR has been merged, but still pending push
8
Fixed (Closed)
The bug fix has gone out in production and is live.
9
Blocked
Something major has gotten into the way of fixing the bug and we expect the SLO to be violated
10
Duplicate (Closed)
This bug is a duplicate of another already filed bug. We are closing this one.
11
Could not Reproduce (Closed)
The bug could not be reproduced and is considered closed.
12
Working as Intended / Not a Bug (Closed)
This is not a bug but rather working as intended.
13
Will not fix (Closed)
This is a bug but we deem it too low priority/impact to be able to commit to fixing it within 6 months.
14
Filed as Feature Request (Closed)
​
20
Untriaged, needs info
Triage for this bug cannot complete because information is needed.
There are no rows in this table
⁠
Issue Sources
Source
Description
Internal
Found internally
Customer
Found by a customer
QA
Found by QA
Compliance or Security Audits
Found via compliance or security audits
Alert
Found via monitoring alerts
HackerOne
​
Pentest
​
There are no rows in this table
⁠

Environments
Environment
Prod
Staging
Head
There are no rows in this table
⁠
Repro'd Device & System
Browser/Device/OS
Chrome
Safari
Firefox
Edge
Arc
Chromium
iOS Mobile App
Android Mobile App
Mobile Browser
Mac OS
Windows OS
Linux OS
Vivaldi
Brave
There are no rows in this table
⁠



P0 Assignment Notification

If a P0 is assigned to someone they get a notification in Slack (see Automations “P0 Assigned Slack Message”).

Weekly team notification

Monday morning Slack message to everyone who has a P0/P1 assigned, listing all assigned P0/P1 bugs
See Automations “Weekly reminder”


2. Clear Sample Data

This doc already has sample data that is useful for demo’s but not useful for using the doc, lets fix that with just the click of a button or three.
⁠
Clear all sample data
⁠
⁠


3. Fill in your Teams

The tables below should be empty assuming you’ve done step 2. Fill
Teams
⁠
with your teams for assignment.

View of Teams
Functional Area
Team
Description
Team Size
Calculate stats
UI/UX Team
Designs and implements the user interface for the web application
3
Stats
Frontend Architecture Team
Develops and maintains the frontend architecture of the web application
4
Stats
Accessibility Team
Ensures the web application is accessible to all users, including those with disabilities
5
Stats
API Team
Develops and maintains the APIs used by the web application
5
Stats
Database Team
Develops and maintains the database used by the web application
5
Stats
DevOps Team
Manages the deployment and monitoring of the web application
5
Stats
Automated Testing Team
Develops and maintains automated testing suites for the web application
6
Stats
Manual Testing Team
Performs manual testing of the web application
2
Stats
Security Team
Ensures the web application is secure and protected from attacks
3
Stats
Scrum Team
Manages the development process using the Scrum methodology
3
Stats
Product Owner Team
Represents the customer and defines the product vision and roadmap
4
Stats
Release Management Team
Manages the release process for the web application
3
Stats
Cloud Infrastructure Team
Manages the cloud infrastructure used by the web application
4
Stats
Network Team
Manages the network infrastructure used by the web application
3
Stats
Server Team
Manages the physical servers used by the web application
3
Stats
There are no rows in this table
⁠

4. Notifications & Automations


P0 Assignment Notification

Capturing Timeline data

Gallery
 
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.