Triage

Definition of Severity (same as Rocket's)

S1

• Key features (or 1st + 2nd level menu features) not working as intended
• Regression from theuser point of view (Definition of “Regression” is as below)
• Crashes (repro. rate/impacted user # will be considered during Priority discussion)

S2

• 3rd and beyond level menu features not working as intended
• Major visual impact

S3

• Minor visual impact

Release blocker

• P1 (not necessary S1) will be blockers by default, as a general guideline

Labels

All lower cases except the S and P system.

• The S-system (S1, S2): following the severity definition above

• The "need triage" label: use it (best with a with short comment) when you feel it's hard to judge the severity or have a different view of the given one (no need to un-label the original severity)

• The P-system (P0, P1, P2): reflecting overall project priority (not necessarily aligns with the bug severity)

• The "need" family (need help, need triage): action needed but not necessarily for a specific person/team

• The "wanted" family (qa wanted, ux wanted, epm wanted): used to ping a specific person/team.

• The categories by function: we'll start with these 5 and adjust when needed

  • home-view
  • collection-view
  • detail-view
  • fab
  • others

• The categories by "design compliance": for issues not complying the Interaction or Visual spec

  • spec-flow
  • spec-string
  • spec-color
  • spec-others

• The "process" label: add this label if you believe this could be a common task for multiple projects. (can be the referenced in the future, or proceduralized)