637
edits
DaveLawrence (talk | contribs) |
DaveLawrence (talk | contribs) |
||
Line 1: | Line 1: | ||
== Bugzilla Field Descriptions == | == Bugzilla Field Descriptions == | ||
{{anchor| | {{anchor|percentage_complete}} | ||
; %Complete | ; %Complete | ||
: How close to 100% done this bug is, by comparing its Hours Worked to its Orig. Est.. | : How close to 100% done this bug is, by comparing its Hours Worked to its Orig. Est.. | ||
Line 34: | Line 34: | ||
; Component | ; Component | ||
: Components are second-level categories; each belongs to a particular Product. Select a Product to narrow down this list. | : Components are second-level categories; each belongs to a particular Product. Select a Product to narrow down this list. | ||
{{anchor|creation_ts}} | {{anchor|creation_ts}} | ||
; Creation date | ; Creation date | ||
Line 46: | Line 43: | ||
; Depends on | ; Depends on | ||
: The bugs listed here must be resolved before this bug can be resolved. | : The bugs listed here must be resolved before this bug can be resolved. | ||
{{anchor|rep_platform}} | {{anchor|rep_platform}} | ||
; Hardware | ; Hardware | ||
: This is the hardware platform against which the bug was reported. | : This is the hardware platform against which the bug was reported. | ||
{{anchor|remaining_time}} | |||
Hours Left | ; Hours Left | ||
:The number of hours of work left on this bug, calculated by subtracting the Hours Worked from the Orig. Est.. | |||
Hours Worked | {{anchor|work_time}} | ||
; Hours Worked | |||
Importance | : The total amount of time spent on this bug so far. | ||
{{anchor|importance}} | |||
; Importance | |||
: The importance of a bug is described as the combination of its Priority and Severity. | |||
Keywords | {{anchor|keywords}} | ||
; Keywords | |||
: You can add keywords from a defined list to bugs, in order to easily identify and group them. | |||
{{anchor|estimated_time}} | |||
; Orig. Est. | |||
: The amount of time that has been estimated it will take to resolve this bug. | |||
{{anchor|op_sys}} | |||
; OS | |||
: This is the operating system against which the bug was reported.= | |||
{{anchor|priority}} | |||
; Priority | |||
: This field describes the importance and order in which a bug should be fixed compared to other bugs. This field is utilized by the programmers/engineers to prioritize their work to be done where P1 is considered the highest and P5 is the lowest. | |||
{{anchor|product}} | |||
; Product | |||
: Bugs are categorised into Products and Components. Select a Classification to narrow down this list. | |||
{{anchor|qa_contact}} | |||
Orig. Est. | ; QA Contact | ||
: The person responsible for confirming this bug if it is unconfirmed, and for verifying the fix once the bug has been resolved. | |||
OS | {{anchor|reporter}} | ||
; Reporter | |||
: The person who filed this bug. | |||
{{anchor|see_also}} | |||
; See Also | |||
: This allows you to refer to bugs in other installations. You can enter a URL to a bug in the 'Add Bug URLs' field to note that that bug is related to this one. You can enter multiple URLs at once by separating them with a comma. You should normally use this field to refer to bugs in other installations. For bugs in this installation, it is better to use the Depends on and Blocks fields. | |||
{{anchor|bug_severity}} | |||
; Severity | |||
: This field describes the impact of a bug. | |||
Priority | |||
Product | |||
QA Contact | |||
Reporter | |||
See Also | |||
Severity | |||
blocker Blocks development and/or testing work | blocker Blocks development and/or testing work | ||
critical crashes, loss of data, severe memory leak | critical crashes, loss of data, severe memory leak | ||
Line 121: | Line 89: | ||
trivial cosmetic problem like misspelled words or misaligned text | trivial cosmetic problem like misspelled words or misaligned text | ||
enhancement Request for enhancement | enhancement Request for enhancement | ||
Summary | {{anchor|short_desc}} | ||
; Summary | |||
: The bug summary is a short sentence which succinctly describes what the bug is about. | |||
{{anchor|target_milestone}} | |||
Target Milestone | ; Target Milestone | ||
: The Target Milestone field is used to define when the engineer the bug is assigned to expects to fix it. | |||
{{anchor|bug_file_loc}} | |||
; URL | |||
URL | : Bugs can have a URL associated with them - for example, a pointer to a web site where the problem is seen. | ||
{{anchor|version}} | |||
; Version | |||
: The version field defines the version of the software the bug was found in. | |||
{{anchor|votes}} | |||
; Votes | |||
Version | : Some bugs can be voted for, and you can limit your search to bugs with more than a certain number of votes. | ||
{{anchor|status_whiteboard}} | |||
Votes | ; Whiteboard | ||
: Each bug has a free-form single line text entry box for adding tags and status information | |||
Whiteboard | |||
edits