BMO/UserGuide/BugFields: Difference between revisions

Revision as of 12:11, 3 June 2017

%Complete: How close to 100% done this bug is, by comparing its Hours Worked to its Orig. Est..

Alias: A short, unique name assigned to a bug in order to assist with looking it up and referring to it in other places in Bugzilla.

Assignee: This is the person in charge of resolving the bug. Every time this field changes, the status changes to NEW to make it easy to see which new bugs have appeared on a person's list.

Blocks: This bug must be resolved before the bugs listed in this field can be resolved.

Bug ID: The numeric id of a bug, unique within this entire installation of Bugzilla.

CC: Users who may not have a direct role to play on this bug, but who are interested in its progress.

Classification: Bugs are categorised into Classifications, Products and Components. classifications is the top-level categorization.

Comment: Bugs have comments added to them by Bugzilla users. You can search for some text in those comments.

Comment Tag: Comments can have arbitrary tags added to them to help with filtering as well as mark comments as spam or abusive.

Component: Components are second-level categories; each belongs to a particular Product. Select a Product to narrow down this list.

Current Estimate: Amount of actual time worked added to the remaining time left is the current time estimate.

Deadline: The date that this bug must be resolved by, entered in YYYY-MM-DD format.

Depends on: The bugs listed here must be resolved before this bug can be resolved.

Duplicates: List of bugs that have been marked a duplicate of the bug currently being viewed.

Hours Left: The number of hours of work left on this bug, calculated by subtracting the Hours Worked from the Orig. Est..

Importance: The importance of a bug is described as the combination of its Priority and Severity.

Keywords: You can add keywords from a defined list to bugs, in order to easily identify and group them.

Mentors: Mentors are users who have offered to help the bug owner with such tasks as setting up a development environment, finding relevant information to fixing the bug, how to submit a patch for review, and finally how to get the fix committed.

Needinfo: More information has been requested from specific individuals, or anyone, to move the bug forward to completion.

Orig. Est.: The amount of time that has been estimated it will take to resolve this bug.

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. See Bugmasters/Process/Triage or for the main Buzilla project, Bugzilla:Priority_System.

Product: Bugs are categorised into Products and Components. Select a Classification to narrow down this list.

QA Contact: The person responsible for confirming this bug if it is unconfirmed, and for verifying the fix once the bug has been resolved.

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.

blocker	Blocks development and/or testing work
critical	Crashes, loss of data, severe memory leak
major	Major loss of function
normal	Regular issue, some loss of functionality under specific circumstances
minor	Minor loss of function, or other problem where easy workaround is present
trivial	Cosmetic problem like misspelled words or misaligned text
enhancement	Request for enhancement

Summary: The bug summary is a short sentence which succinctly describes what the bug is about.

Target Milestone: The Target Milestone field is used to define when the engineer the bug is assigned to expects to fix it.

Triage Owner: User that is responsible for triaging bugs that are assigned to a specific component.

URL: Bugs can have a URL associated with them - for example, a pointer to a web site where the problem is seen.

Version: The version field defines the version of the software the bug was found in.

Votes: Some bugs can be voted for, and you can limit your search to bugs with more than a certain number of votes.

Whiteboard: Each bug has a free-form single line text entry box for adding tags and status information

@@ Line 81: / Line 81: @@
 {{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.
+: 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. See [[Bugmasters/Process/Triage]] or for the main Buzilla project, [[Bugzilla:Priority_System]].
 {{anchor|product}}
 ; Product