Difference between revisions of "Bugzilla user notes"
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Bugzilla is an efficient way to pass information back to developers. | |
| − | + | Please take care to learn the procedures, so that the information you send will be as effective as possible. | |
| − | + | When you login to Bugzilla using [https://krikkit.srv.ualberta.ca/bugzilla/enter_bug.cgi this URL], you'll see the OTS Bug Manager page. | |
| − | 1. blocker - Fail Prevents function from being used, no work around | + | Log a bug as follows: |
| + | # '''component''': select the component from the scrolling list at the upper right. Components more or less align to MuDoc pages; select the closest match. If you aren't sure, or you've noted a pervasive problem, select "Miscellaneous". | ||
| + | # '''platform''': enter your user platform (computer type) on the left. Some bugs may be platform specific. The system will attempt to guess platform, but make sure the guess is correct | ||
| + | # '''OS (operating system)''': again, the system will guess; correct if needed | ||
| + | # '''priority''': optionally, you can assign a priority, although the bug severity will also imply priority to some degree. | ||
| + | # '''bug severity''': This is important. Use the severity code definitions as supplied below. Now, skip the next few boxes until you come to: | ||
| + | # '''summary''': enter a short descriptor for the problem you've identified | ||
| + | # '''description''': provide a detailed description, including the username, MuDoc page, other relevant details (e.g. keyword, asset name), and pasting in any crash error message that may have occurred. | ||
| + | |||
| + | |||
| + | '''Bug severity code definitions''' | ||
| + | |||
| + | (extracted from [http://folkways.tapor.ualberta.ca/~michaelf/MuDoc-%20User%20Acceptance%20Test%20Plan%20-%20revised%205%20(final).pdf UAT plan]) | ||
| + | |||
| + | Note that codes 1 to 4 are considered "fails". Code 5 is ambiguous. Codes 6 and 7 are passes. | ||
| + | |||
| + | 1. blocker - Fail Prevents function from being used, no work around; bug is | ||
blocking progress on multiple fronts | blocking progress on multiple fronts | ||
| Line 12: | Line 28: | ||
is possible | is possible | ||
| − | 4. | + | 4. trivial – Fail A problem not affecting the actual function, a typo |
would be an example | would be an example | ||
| − | 5. | + | 5. normal – A problem making a function difficult to use but no |
special work around is required – Tester pass fail is | special work around is required – Tester pass fail is | ||
ignored | ignored | ||
| − | 6. | + | 6. minor - Pass A problem not affecting the actual function, but the |
behavior is not natural | behavior is not natural | ||
7. pass - No bug detected | 7. pass - No bug detected | ||
| − | + | --- | |
| − | |||
| − | |||
| − | |||
| − | + | [Note: 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.] | |
Latest revision as of 14:57, 1 March 2007
Bugzilla is an efficient way to pass information back to developers. Please take care to learn the procedures, so that the information you send will be as effective as possible.
When you login to Bugzilla using this URL, you'll see the OTS Bug Manager page.
Log a bug as follows:
- component: select the component from the scrolling list at the upper right. Components more or less align to MuDoc pages; select the closest match. If you aren't sure, or you've noted a pervasive problem, select "Miscellaneous".
- platform: enter your user platform (computer type) on the left. Some bugs may be platform specific. The system will attempt to guess platform, but make sure the guess is correct
- OS (operating system): again, the system will guess; correct if needed
- priority: optionally, you can assign a priority, although the bug severity will also imply priority to some degree.
- bug severity: This is important. Use the severity code definitions as supplied below. Now, skip the next few boxes until you come to:
- summary: enter a short descriptor for the problem you've identified
- description: provide a detailed description, including the username, MuDoc page, other relevant details (e.g. keyword, asset name), and pasting in any crash error message that may have occurred.
Bug severity code definitions
(extracted from UAT plan)
Note that codes 1 to 4 are considered "fails". Code 5 is ambiguous. Codes 6 and 7 are passes.
1. blocker - Fail Prevents function from being used, no work around; bug is 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
---
[Note: 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.]
