# Problem Report Fields

### Severity

The severity of the problem. Accepted values include:

- critical:
  The product, component or concept is completely non operational. No workaround is known.
- serious:
  The product, component or concept is not working properly. Problems that would otherwise be considered critical are rated serious when a workaround is known.
- non-critical:
  The product, component or concept is working in general, but lacks features, has irritating behavior, does something wrong, or doesn't match its documentation.

The default value is serious.

### Priority

How soon the originator requieres a solution. Accepted values include:

- high:
  A solution is needed as soon as possible.
- medium:
  The problem should be solved in the next release.
- low:
  The problem should be solved in a future release.

The default value is medium.

### Class

The class of a problem can be one of the following:

- sw-bug:
  A general product problem.
- doc-bug:
  A problem with documentation.
- change-request:
  A request for a change in behavior, etc.
- support:
  A support problem or question.
- duplicate pr-number:
  Duplicate PR. Pr-number should be the number of the original PR.

The default value is sw-bug.

### State

This is the current state of the problem report. It can be one of the following:

- open:
  The problem report has been filed and the person responsible for that category has been informed.
- assigned:
  The problem has been assigned to a specific person for solving.
- feedback:
  A possible solution or a request for further information has been sent to the submitter.
- suspended:
  Work on the problem has been postponed.
- moved:
  The report was incorrectly filed and it has been moved to the correct Domain/Category.
- closed:
  The solution to the problem has been fully tested and shown to work.

### Originator

Originator's real name. The default is the value of the originator's enviroment variable NAME.

### Email address

Originator's email address.

### Organization

The originator's organization. The default value is set with the variable DEFAULT_ORGANIZATION in the send-pr shell script.

### Release

Release or version number of the product, component or concept.

### Summary

One-line summary of the problem. This information will be copied to the Subject: line when submitting a Problem Report.

### Category

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.

### Environment

Description of the environment where the problem occured: machine architecture, operating system, host and target types, libraries, pathnames, etc. To fill in this field, execute the command uname -a and copy the result here.

### Description

Precise description of the problem.

### How to repeat

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.

### Fix

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 she has solved the problem.

For further information please refer to Problem Report format