-[This document is aimed primarily at people who have used Bugzilla -before the UNCONFIRMED state was implemented. It might be helpful for -newer users as well.] -
- -- -New bugs in some products will now show up in a new state, -UNCONFIRMED. This means that we have nobody has confirmed that the -bug is real. Very busy engineers will probably generally ignore -UNCONFIRMED that have been assigned to them, until they have been -confirmed in one way or another. (Engineers with more time will -hopefully glance over their UNCONFIRMED bugs regularly.) -
- --The page describing bug fields has been -updated to include UNCONFIRMED. -
- --There are two basic ways that a bug can become confirmed (and enter -the NEW) state. -
- --One implication of this is that it is worth your time to search the -bug system for duplicates of your bug to vote on them, before -submitting your own bug. If we can spread around knowledge of this -fact, it ought to help cut down the number of duplicate bugs in the -system. -
- --Users now have a certain set of permissions. To see your permissions, -check out the -user preferences page. -
- --If you have the "Can confirm a bug" permission, then you will be able -to move UNCONFIRMED bugs into the NEW state. -
- --If you have the "Can edit all aspects of any bug" permission, then you -can tweak anything about any bug. If not, you may only edit those -bugs that you have submitted, or that you have assigned to you (or -qa-assigned to you). However, anyone may add a comment to any bug. -
- --Some people (initially, the initial owners and initial qa-contacts for -components in the system) have the ability to give the above two -permissions to other people. So, if you really feel that you ought to -have one of these permissions, a good person to ask (via private -email, please!) is the person who is assigned a relevant bug. -
- --An initial stab was taken to decide who would be given which of the -above permissions. This was determined by some simple heurstics of -who was assigned bugs, and who the default owners of bugs were, and a -look at people who seem to have submitted several bugs that appear to -have been interesting and valid. Inevitably, we have failed to give -someone the permissions they deserve. Please don't take it -personally; just bear with us as we shake out the new system. -
- --People with one of the two bits above can easily confirm their own -bugs, so bugs they submit will actually start out in the NEW state. -They can override this when submitting a bug. -
- --People can ACCEPT or RESOLVE a bug assigned to them, even if they -aren't allowed to confirm it. However, the system remembers, and if -the bug gets REOPENED or reassigned to someone else, it will revert -back to the UNCONFIRMED state. If the bug has ever been confirmed, -then REOPENing or reassigning will cause it to go to the NEW or -REOPENED state. -
- --Note that only some products support the UNCONFIRMED state. In other -products, all new bugs will automatically start in the NEW state. -
- --There probably ought to be a way to get a bug back into the -UNCONFIRMED state, but there isn't yet. -
- --If a person has submitted several bugs that get confirmed, then this -is probably a person who understands the system well, and deserves the -"Can confirm a bug" permission. This kind of person should be -detected and promoted automatically. -
- --There should also be a way to automatically promote people to get the -"Can edit all aspects of any bug" permission. -
- --The "enter a new bug" page needs to be revamped with easy ways for new -people to educate themselves on the benefit of searching for a bug -like the one they're about to submit and voting on it, rather than -adding a new useless duplicate. -
- -- -Last modified: Sun Apr 14 12:55:14 EST 2002 - -
- diff --git a/help.html b/help.html deleted file mode 100644 index a7c93cb45..000000000 --- a/help.html +++ /dev/null @@ -1,70 +0,0 @@ - - - - - --The way the query works, if you have nothing checked in a box, -then all values for that field are legal, for example if you checked nothing -in any of the boxes, you would get the entire bug list. -
-The default value of this form should correspond roughly to a "personal" -bug list. -
-For example, if you wanted to see all bugs reported against the X platform -and assigned to jwz, you could ask for all bugs assign to jwz, then -edit the URL in the "Location" box, adding the clause "&rep_platform=X-Windows" -to the URL. -
-Here is a list of some of the field names you could use for additional -unsupported searches ... - -
-version -rep_platform -op_sys -reporter area -bug_file_loc -short_desc --
Bugzilla uses several non-standard Netscape extentions, but this does not seem -to case any problem with other browsers. The lynx browser does work, but lynx -seems to cache results of a .cgi. You'll sometimes need to press CONTROL-R to reload -the screen to see an update. - - diff --git a/helpemailquery.html b/helpemailquery.html deleted file mode 100644 index 5c4527a78..000000000 --- a/helpemailquery.html +++ /dev/null @@ -1,38 +0,0 @@ - -
- --This used to be simpler, but not very powerful. Now it's really -powerful and useful, but it may not be obvious how to use it... -
- --To search for bugs associated with an email address: -
- --You can look for up to two different email addresses; if you specify -both, then only bugs which match both will show up. This is useful to -find bugs that were, for example, created by Ralph and assigned to -Fred. -
- --You can also use the drop down menus to specify whether you want to -match addresses by doing a substring match, by using regular -expressions, or by exactly matching a fully specified email address. -
- - diff --git a/how_to_mail.html b/how_to_mail.html deleted file mode 100644 index b60c41688..000000000 --- a/how_to_mail.html +++ /dev/null @@ -1,90 +0,0 @@ - - - - - - - -- -
-@FIELD-LABEL VALUE - LABEL Legal Values - Priority critical major normal minor trivial - Type BUG RFE - Product Cheddar - Platform PC X-Windows Macintosh All - Area CODE JAVA TEST BUILD UI PERF - Version version 2.0b1 2.0b2 2.0b2 2.0b4 2.1a0 2.1a1 2.1b0 2.1b1 2.1b2 - OS Windows 3.1 Windows 95 Windows NT System 7 System 7.5 - AIX BSDI HP-UX IRIX Linux OSF/1 Solaris SunOS other - Summary -anything- - URL -anything- - Assign someone in eng - - -and - -@description - This tells the bug parse to stop looking for control lines, - allowing the bug description to contain lines which start with @ -- -There are default values for all these fields. If you don't specify a -Summary, the subject of the mail message is used.
- -If you specify an illegal value, the default value is used, the -bug is assigned to you, and the answerback message will describe -the error.
- -After the bug is posted, you will get mail verifying the posting -and informing you of the bug number if you wish to fix any -mistakes made by the auto-processor.
- -EXAMPLE:
- - -
- % Mail bugzilla - Subject: WinFE crashes with GPF when I pour beer on my keyboard - @priority critical - @platform PC - @assign troy - - After the beer bash I emptied the rest of the keg onto my keyboard - and my sharp build of Navigator got a GPF. - . - -- - diff --git a/notargetmilestone.html b/notargetmilestone.html deleted file mode 100644 index 1cedb1aca..000000000 --- a/notargetmilestone.html +++ /dev/null @@ -1,16 +0,0 @@ - - -
-No target milestones have been defined for this product. You can set -the Target Milestone field to things, but there is not currently any -agreed definition of what the milestones are. -
- - - -- cgit v1.2.3-24-g4f1b