Professional Documents
Culture Documents
Process documentation
Bugzilla fields
When opening a bugzilla, use the following definitions of severity and priority to categorize the bugzilla
correctly. Typically a high severity means a matching high priority, but it is possible to have a bugzilla
with a high severity and a low priority. For example, if the defect is a problem that blocks use of a
enhancement, but that enhancement is a corner case that has few (if any) users, then that bugzilla
would be high severity but low priority.
Priority Definitions
Priority Definition
P1 Cannot ship without this enhancement
P2 Highly desirable and planned for this release,
but not stop ship
P3 Of interest, but not planned or expected in this
release
P4 Not used by TPTP
P5 Not used by TPTP
Severity Definitions
Severity Definition
blocker Prevents function from being used, no work
around, blocking progress on multiple fronts
critical Prevents function from being used, no work
around
major Prevents function from being used, but a work
around is possible
normal A problem making a function difficult to use but
no special work around is required
minor A problem not affecting the actual function, but
the behavior is not natural
trivial A problem not affecting the actual function, a
typo would be an example
Bugzilla Process
Note that the priority level chosen by the reporter is a guideline for TPTP, and may or may
not be changed by the Requirements Group when it's time to create a TPTP plan.
5. The reporter does not adjust the Target Milestone of the bugzilla. Only the assignee may
adjust the Target Milestone of the bugzilla. The Target Milestone of an enhancement may
be set by the assignee to one of the following:
• <release> [<iteration>] if the enhancement is committed into a TPTP plan based on guidance from
the AG and Project Lead.
• The defect is resolved without a change (e.g. INVALID, WONTFIX, LATER, REMIND,
WORKSFORME and duplicate of another defect).
If the assignee disagrees with the severity, the assignee negotiates with the reporter to adjust.
Likewise, if the reporter disagrees with the priority or target milestone, the reporter will negotiate with
the assignee to adjust. However, typically each will not directly change the others' settings.