The editing form is for changing problem reports. In the above part there is a change form, in the bottom part current values of the problem report are displayed.
You change the problem simply by changing appropriate values and pressing the Submit button. For description of most field values see the Submitting help. There are some special things about editing as described in the following sections.
It is necessary to select, who is changing the report. If you are registered in the bug tracking system, just select your identity. If not, select either submitter (if you are the one, who submitted the problem report), or unknown (otherwise).
Though you can change the subject field, it is often not a good idea to do so. Subjects are important for easy orientation in the problems and their changes usually make the orientation harder. So it is good to change them only if it improves the arrangement.
There are more classes offered in editing than in submitting. Class field usually includes the following values in editing (they can vary depending on a particular bug database):
You can change the person responsible for the problem here. It is usually not a good idea to change this without previously contacting both the old and new responsible person.
All submitted problem reports are in the open state initially. When they are solved, their state is changed. Usual possible state values (they can vary depending on a particular database) are:
If you change one of these fields, you must describe the reason for doing this. This information is sent to all interested parties. When changing the state to feedback or closed, it is often good idea to describe how the problem was fixed, it can be useful in future.
When you edit one of Description, How To Repeat, How To Fix, or Environment fields, the edited text is appended to the current text of the field. This means no previous information in these fields is lost.
Do not make new proposals not related directly and very closely to the edited problem when editing it. Submit new problem report instead, which will be solved separately.