Skip to content

(QA) Bug writing format

lpietrucha edited this page Apr 8, 2014 · 2 revisions

Basic fields

Summary: [Platform][Area] Short summary

Issue Type: Bug

Assignee: Automatic (or per request by Leader)

Description

Preconditions:

...

Repro steps:

  1. ...

  2. ...

  3. ...

Expected result:

...

Actual result:

...

Other important fields

Priority:

  • Blocker - Crash issue/Testing blocked/Catastrophic or Major Functionality blocked (No workaround)
  • Critical - Feature failure (no workaround)
  • Major - Feature impairment (workaround exists)
  • Minor - Minor issue (UI text, very little inconvenience to user)

Critical/Blocker/Major should be fixed in the current sprint

Minor are stored in backlog so team can pick it up during planning

Fix Version: Please use current sprint for Critical/Blocker/Major and leave empty for Minor issues

Components: QA, platform which you are working on (Android/WP/iOS)