![]() ![]() You can change how much depth to show, and you can hide resolved bugsįrom this page. The dependency relationships of the bug as a tree structure. On), or this bug stops other bugs being fixed (blocks), their If this bug cannot be fixed unless other bugs are fixed (depends Track of sets of bugs that you personally care about, using your ownĬlassification system. Them won’t send any notifications to other users. Personal Tags: Unlike Keywords which are global and visible by all users, Personal TagsĪre personal and can only be viewed and edited by their author. Keywords: The administrator can define keywords which you can use to tag andĬategorise bugs-e.g. *Whiteboard: A free-form text area for adding short notes and tags to a bug. URL: A URL associated with the bug, if any. *QA Contact: The person responsible for quality assurance on this bug. Assigned To: The person responsible for fixing the bug. Restricted to numbers, though-you can use any text strings, suchĪs dates. The Bugzilla Project’s milestones for futureīugzilla versions are 4.4, 5.0, 6.0, etc. *Target Milestone: A future version by which the bug is toīe fixed. YouĬan also use this field to indicate whether a bug is an enhancement (“application unusable”) to trivial (“minor cosmetic issue”). The Severity field indicates how severe the problem is-from blocker It’s a good idea not to change this on other people’s bugs. Or someone else with authority to direct their time such as a project The Priority field is used to prioritize bugs, either by the assignee, Hardware (Platform and OS): These indicate the computing environment where the bug wasįound. It is used to indicate the version(s) affected by Version: The “Version” field usually contains the numbers or names of released Product and Component: Bugs are divided up by Product and Component, with a Product Alias: A unique short text name for the bug, which can be used instead of theīug number. Status and Resolution on your installation should be documented in theĬontext-sensitive help for those items. Status (and Resolution): These define exactly what state the bug is in-from not evenīeing confirmed as a bug, through to being fixed and the fixĬonfirmed by Quality Assurance. Summary: A one-sentence summary of the problem, displayed in the header next to Fields marked * may not be present on every Note that the labels for most fields are hyperlinks Ĭlicking them will take you to context-sensitive help on that The core of Bugzilla is the screen which displays a particularīug. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |