Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 83112 - Many help related bugs
Many help related bugs
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
All Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: PnT DevOps Devs
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-01-30 08:42 EST by David Balažic
Modified: 2013-06-23 23:08 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-04 16:30:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Balažic 2003-01-30 08:42:34 EST
Description of problem:

On the query page ( https://bugzilla.redhat.com/bugzilla/query.cgi ) the 
word "Component text:" is not a link to help, while on the bug entry page ( 
20Beta ) it is a link to help.

https://bugzilla.redhat.com/bugzilla/queryhelp.cgi#priority and
https://bugzilla.redhat.com/bugzilla/bug_status.cgi#priority are missing 
description of priority value "contract".

On the query page, the field "A Comment" is not a link to help , altough there 
is a description available on page 
The same holds for "URL" , "Whiteboard".

The fileds "Bug Changes" have no link to help, but there is a descrition on the 
queryhelp.cgi page named "Inclusion/Exclusion Options" ( which was written for 
an earlier version of bugzilla, it seems ).
Comment 1 David Lawrence 2006-04-08 14:03:00 EDT
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.
Comment 2 David Lawrence 2008-09-16 12:49:49 EDT
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.

Note You need to log in before you can comment on or make changes to this bug.