Gallery
Quality tracker
Share
Explore

icon picker
Setup

1. Setup your prioritization and other lookup tables


Set Priorities and SLO
2
Priority
Criteria
SLO
Timeline
1
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
2
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
3
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
4
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
1
Index
Status
Description
Closes Bug
Is untriaged
1
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
2
Untriaged
New bug, the team acknowledged the bug belongs to them and is not a P0 but not yet fully triaged
3
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
4
5
In Progress
The engineer assigned has started to work on fixing the bug.
5
6
PR Merged (Code Complete)
The code for fixing the bug is complete and the last PR has been merged, but still pending push
6
8
Fixed (Closed)
The bug fix has gone out in production and is live.
7
9
Blocked
Something major has gotten into the way of fixing the bug and we expect the SLO to be violated
8
10
Duplicate (Closed)
This bug is a duplicate of another already filed bug. We are closing this one.
9
11
Could not Reproduce (Closed)
The bug could not be reproduced and is considered closed.
10
12
Working as Intended / Not a Bug (Closed)
This is not a bug but rather working as intended.
11
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.
12
14
Filed as Feature Request (Closed)
13
20
Untriaged, needs info
Triage for this bug cannot complete because information is needed.
There are no rows in this table
Issue Sources
1
Source
Description
1
Internal
Found internally
2
Customer
Found by a customer
3
QA
Found by QA
4
Compliance or Security Audits
Found via compliance or security audits
5
Alert
Found via monitoring alerts
6
HackerOne
7
Pentest
There are no rows in this table

Environments
1
Environment
1
Prod
2
Staging
3
Head
There are no rows in this table
Repro'd Device & System
1
Browser/Device/OS
1
Chrome
2
Safari
3
Firefox
4
Edge
5
Arc
6
Chromium
7
iOS Mobile App
8
Android Mobile App
9
Mobile Browser
10
Mac OS
11
Windows OS
12
Linux OS
13
Vivaldi
14
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 with your teams for assignment.

View of Teams
2
Functional Area
Team
Description
Team Size
Calculate stats
1
Frontend Development
UI/UX Team
Designs and implements the user interface for the web application
3
Stats
2
Frontend Development
Frontend Architecture Team
Develops and maintains the frontend architecture of the web application
4
Stats
3
Frontend Development
Accessibility Team
Ensures the web application is accessible to all users, including those with disabilities
5
Stats
4
Backend Development
API Team
Develops and maintains the APIs used by the web application
5
Stats
5
Backend Development
Database Team
Develops and maintains the database used by the web application
5
Stats
6
Backend Development
DevOps Team
Manages the deployment and monitoring of the web application
5
Stats
7
Quality Assurance
Automated Testing Team
Develops and maintains automated testing suites for the web application
6
Stats
8
Quality Assurance
Manual Testing Team
Performs manual testing of the web application
2
Stats
9
Security
Security Team
Ensures the web application is secure and protected from attacks
3
Stats
10
Project Management
Scrum Team
Manages the development process using the Scrum methodology
3
Stats
11
Project Management
Product Owner Team
Represents the customer and defines the product vision and roadmap
4
Stats
12
Project Management
Release Management Team
Manages the release process for the web application
3
Stats
13
Infrastructure
Cloud Infrastructure Team
Manages the cloud infrastructure used by the web application
4
Stats
14
Infrastructure
Network Team
Manages the network infrastructure used by the web application
3
Stats
15
Infrastructure
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

Share
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.