Node:edit-pr, Next:query-pr, Previous:send-pr, Up:GNATS user tools
edit-pr to make changes to existing PRs in the database.
This tool can be invoked both from a shell prompt or from within GNU
edit-pr first examines the PR you wish to edit and locks it if it
is not already locked. This is to prevent you from editing a PR at the
same time as another user. If the PR you wish to edit is already in the
process of being edited,
edit-pr tells you the name of the person
who owns the lock.
You may edit any non-readonly fields in the database. We recommend that
you avoid deleting any information in the TEXT and MULTITEXT
fields (such as
(see Problem Report format). We also recommend that you
record the final solution to the problem in the
Fix field for
future reference. Note that heavily customized installations of
GNATS may have differently named fields, and sites using such
installations should provide their own set of routines and instructions
regarding how PRs should be treated throughout their life span.
After the PR has been edited, it is then resubmitted to the database,
and the index is updated (see The
For information on
pr-edit, the main driver for
see Internal utilities.
If you change a field that requires a reason for the change, such as the
State fields in the default configuration,
edit-pr prompts you to supply a reason for the change. A message
is then appended to the
Audit-Trail field of the PR with the
changed values and the change reason.
Depending on how the database is configured, editing various fields in
the PR may also cause mail to be sent concerning these changes. In the
default configuration, any fields that generate
entries will also cause a copy of the new
Audit-Trail message to
edit-prfrom the shell