Difference between revisions of "Bugzilla user notes"
| Line 2: | Line 2: | ||
'''Severity Definitions''' | '''Severity Definitions''' | ||
| − | (extracted from UAT plan) | + | (extracted from [http://folkways.tapor.ualberta.ca/~michaelf/MuDoc-%20User%20Acceptance%20Test%20Plan%20-%20revised%205%20(final).pdf UAT plan]) |
1. blocker - Fail Prevents function from being used, no work around, | 1. blocker - Fail Prevents function from being used, no work around, | ||
Revision as of 16:11, 22 January 2007
Bugzilla codes: Severity Definitions
(extracted from UAT plan)
1. blocker - Fail Prevents function from being used, no work around, blocking progress on multiple fronts
2. critical - Fail Prevents function from being used, no work around
3. major - Fail Prevents function from being used, but a work around is possible
4. Trivial – Fail A problem not affecting the actual function, a typo would be an example
5. Normal – A problem making a function difficult to use but no special work around is required – Tester pass fail is ignored
6. Minor - Pass A problem not affecting the actual function, but the behavior is not natural
7. pass - No bug detected
All minor (number 6) will have 20 hours total time allocated to attempt fixes. All passes will assign a number of 5, 6 or 7 and fails will assign a 1,2,3,4 or 5.
Other notes:
- Add username, keyword, and asset information to each bug description whenever possible
- if the program crashes, cut and paste crash information into the bug report
