The severity of the problem. Accepted values include:
How soon the originator requieres a solution. Accepted values include:
The class of a problem can be one of the following:
Originator's real name. The default is the value of the originator's enviroment variable NAME.
Originator's email address.
The originator's organization. The default value is set with the variable DEFAULT_ORGANIZATION in the send-pr shell script.
Day and time when problem occurred. Defaults to PR's opening time.
Day and time when problem ended. No default.
Release or version number of the product, component or concept.
One-line summary of the problem. This information will also be copied to the Subject: line when submitting a Problem Report.
The name of the product, component or concept where the problem lies. The values for this field are defined by the Support Site. See also The Categories file.
Description of the environment where the problem occured: machine architecture, operating system, host and target types, libraries, pathnames, etc. To fill in this field for a UNIX system, execute the command uname -a and copy the result here. Other systems may have similar facilities: if not, fill info by hand. More info you supply, better support people may help you.
Precise description of the problem. More details you supply, better support peoples may help you.
Example code, input, or activities to reproduce the problem. The support organization uses example code both to reproduce the problem and to test whether the problem is fixed. Include all precondition, inputs, outputs, conditions after the problem, and symptoms. Any additional important information should be included. Include all the details that would be necessary for someone else to recreate the problem reported, however obvious. Sometimes seemingly arbirary or obvious information can point the way toward a solution. See also Helpful hints.
A description of a solution to the problem, or a patch which solves the problem. This field is most often filled in at the Support Site. We provide it to the submitter in case he has solved the problem on his own.
A free-text field where to store notes, impressions and whatever operator requires it's better to keep somewhere trace of.
A formatted-text field where all changes occurred to PR are recorded. Managed directly by GNATS System, its sub-fields explain clearly what action has been taken and when.
For further information please refer to Problem Report format