-
Notifications
You must be signed in to change notification settings - Fork 17
(QA) Bug writing format
lpietrucha edited this page Apr 8, 2014
·
2 revisions
Summary: [Platform][Area] Short summary
Issue Type: Bug
Assignee: Automatic (or per request by Leader)
Preconditions:
...
Repro steps:
-
...
-
...
-
...
Expected result:
...
Actual result:
...
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)