Table of Contents
Bug Tracking
Severity
| blocker | Can’t even start FF because of this bug |
| critical | FF crashes |
| major | More important than an average bug |
| normal | Just an average bug that needs to be fixed |
| minor | Less important than an average bug |
| trivial | Little tweak that should be performed when we have a chance |
| enhancement | A new feature |
Priority
- A private information. Should be used to prioritize working on own bugs. Manager can use this to increase priority in the context of bugs assigned to a developer.
Target Milestone
- Never use target milestone when entering a bug.
- Never change the milestone when editing a bug.
- Use escalate flag if the bug needs management attention and should be fixed soon - managements gets email about this.
- If you have a bug which does not have target milestone, please analyze how important it is and set escalate or postpone accordingly. Target milestone will be set by management.
- Bugs with postpone requested or approved do not appear on your “My Todo Now” and “My Todo Next”, they do appear on workload.
Flags
- Point mouse over the flag to see a hint.
- Use “?” to request a decision.
Time Tracking
- Please estimate your bugs, it is no problem if you make wrong estimation.
- Whenever you are entering a bug, put there your original estimation, even if you have only rough idea. If you do not have a clue, leave it empty.
- When you accept the bug, you know you are the right person, please change “Hours Left” to your current estimation. This may be the same as original.
- Once a week (on Friday) or on request or when closing a bug please update “Hours Left” and “Hours Worked”. Put there values that you expect by the end of the current day.
