/etc/gnats/defaults/states is in gnats-user 4.1.0-5.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 | # Possible states for a PR.
#
# Any line which begins with a `#' is considered a comment, and GNATS
# will ignore it.
#
# Each entry has the format:
#
# state[:type[:description]]
#
# that is, any of the following are okay:
#
# suspended
# suspended:closed
# suspended:closed:No solution yet, work on it also suspended for the time being.
# suspended::No solution yet, work on it also suspended for the time being.
#
# * `state' is the name of the state; it can contain alphanumerics,
# "-", "_", and ".", but no other characters.
#
# * `type' is the optional name of the state type; it can contain
# alphanumerics, "-", "_", and ".", but no other characters. The
# only defined state types are "open" and "closed". The "open" state
# isn't currently used for anything. Changing the state of a PR to
# any state of type "closed" will set the Closed-Date field with a
# time stamp. Changing the state of a PR from one "closed" state to
# another will leave the Closed-Date field as it was. Changing the
# state of a PR from any state of type "closed" to a non-closed
# state will clear the Closed-Date field. The --skip-closed option
# of query-pr refers to all states of type ``closed'', not to a
# specific state name of ``closed''.
#
# `description' is an optional one-line description of what this
# state means. Any character is okay in the description; a newline
# ends it, however. GNATS does not currently use the description
# for anything, but certain external tools (such as TkGnats and
# Gnatsweb) look for it, so it's a good idea include one for every
# state.
#
# The first listed state is the default state for an incoming Problem
# Report. The last listed state is considered one of the final
# ("closed") states for a Problem Report and will be forced to have a
# type of "closed". Once a PR is in this state, its life-cycle is
# usually over unless someone re-opens it.
# It is recommended that the first state always be "open", as some
# external tools may look for this to determine whether or not a PR
# has been acted on. Change at your own risk.
open::Default state for a new problem report.
# The middle states are what you think is useful; customize them as
# you wish. You can add or delete states here; it is not required
# that there be three of them. Depending on your definition of the
# suspended state, you may want to set its type to be "closed".
analyzed::Problem examined, understood; difficulty of solution estimated.
suspended::No solution yet, work on it also suspended for the time being.
feedback::Problem solved, now awaiting originator's reaction to fix.
# Where old PRs go to die. Like "open", there may be external tools
# which look for this state to know if a PR is still active. Change
# at your own risk. The last state will be forced to be a "closed" type
# even if you specify something else.
closed:closed:This PR no longer active; it is resolved or otherwise defunct.
|