Nowadays we use the keywords filter:ĭescription: Use when a bug report has multiple bugs reported in a single bug report. Also not appropriate for “needsWindows” (setting version to “Windows(all)” is sufficient, but if a particular version of Windows is needed (such as XP) it is appropriate, please see more appropriate explanation at the section #Specific OS Requirement.ĭescription: Used when the issue is an interoperability issue with Microsoft Office (doc/docx, xls/xlsx, etc. Not appropriate for “needsMSO” as Microsoft Office is relatively common but if the bug only affects Microsoft Office 2013 then using “needsMSO2013” is appropriate.
BUGZILLA UPDATE SOFTWARE
Use: Only used for unique software requirement. Used mostly by QA members and developers.ĭescription: Used to highlight a particular piece of software that is required to triage the bug. Use: Generally used when the testing environment is different than the testing environment of the bug reporter so closing the bug as WORKSFORME status is less applicable. Includes information about what version was used and the operating system of the tester. Should always include “confirmed:” then version and then OS.ĭescription: Used when you are unable to reproduce the bug but are not comfortable closing the bug as LINK
Use: Not frequently used but can be used when wanting to add more information to a confirmed bug. Do NOT use the Whiteboard for random comments!ĭescription: Can be used to say that the bug was confirmed on a particular OS and using a particular version of LibreOffice.first word lower-case, following words Upper-Case, and no inter-word spaces That being said, we do encourage users and QA to only use tags that are on the approved list. While the Keywords field has a set list of allowed terms, there are no restrictions on what can go in the Whiteboard field. We've recently migrated many common Whiteboard Tags to the Keywords field. The Whiteboard text box has historically been where QA puts specific terms to help organize our bug tracker. For a complete explanation with all Whiteboard tags please visit Advanced.
BUGZILLA UPDATE HOW TO
If you don’t know how to do this, see the instructions below.This page is for beginners and only has the basics of using the Whiteboard text box in Bugzilla. Add a custom field in Bugzilla, named cf_pt_id (Type is ‘ Free Text‘).
BUGZILLA UPDATE UPDATE
In Extension.pm, update the CONFIG_API_TOKEN constant (line 33).Change the directory’s name to “PractiTest”.Copy this folder to the ‘ Extensions‘ directory of bugzilla.
BUGZILLA UPDATE INSTALL
0 kommentar(er)
