diff options
Diffstat (limited to 'docs/en')
| -rw-r--r-- | docs/en/images/bzLifecycle.xml | 4 | ||||
| -rw-r--r-- | docs/en/xml/administration.xml | 8 | ||||
| -rw-r--r-- | docs/en/xml/installation.xml | 2 |
3 files changed, 7 insertions, 7 deletions
diff --git a/docs/en/images/bzLifecycle.xml b/docs/en/images/bzLifecycle.xml index dda8ac48a..dc1df1e17 100644 --- a/docs/en/images/bzLifecycle.xml +++ b/docs/en/images/bzLifecycle.xml @@ -419,7 +419,7 @@ <dia:attribute name="text"> <dia:composite type="text"> <dia:attribute name="string"> - <dia:string>#NEW#</dia:string> + <dia:string>#CONFIRMED#</dia:string> </dia:attribute> <dia:attribute name="font"> <dia:font family="sans" style="80" name="Helvetica"/> @@ -467,7 +467,7 @@ <dia:attribute name="text"> <dia:composite type="text"> <dia:attribute name="string"> - <dia:string>#ASSIGNED#</dia:string> + <dia:string>#IN_PROGRESS#</dia:string> </dia:attribute> <dia:attribute name="font"> <dia:font family="sans" style="80" name="Helvetica"/> diff --git a/docs/en/xml/administration.xml b/docs/en/xml/administration.xml index 2a05404f1..884284365 100644 --- a/docs/en/xml/administration.xml +++ b/docs/en/xml/administration.xml @@ -771,7 +771,7 @@ <listitem> <para> Set this to the number of days you want to let bugs go - in the NEW or REOPENED state before notifying people they have + in the CONFIRMED state before notifying people they have untouched new bugs. If you do not plan to use this feature, simply do not set up the whining cron job described in the installation instructions, or set this value to "0" (never whine). @@ -1239,7 +1239,7 @@ basis. The number of <quote>votes</quote> available to users is set per-product, as is the number of votes required to move a bug automatically from the UNCONFIRMED - status to the NEW status. + status to the CONFIRMED status. </para> <para> @@ -2547,7 +2547,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT This allows developers to gauge user need for a particular enhancement or bugfix. By allowing bugs with a certain number of votes to automatically move from "UNCONFIRMED" to - "NEW", users of the bug system can help high-priority bugs garner + "CONFIRMED", users of the bug system can help high-priority bugs garner attention so they don't sit for a long time awaiting triage.</para> <para>To modify Voting settings:</para> @@ -2576,7 +2576,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT <para><emphasis>Number of votes a bug in this product needs to automatically get out of the UNCONFIRMED state</emphasis>: Setting this field to "0" disables the automatic move of - bugs from UNCONFIRMED to NEW. + bugs from UNCONFIRMED to CONFIRMED. </para> </listitem> diff --git a/docs/en/xml/installation.xml b/docs/en/xml/installation.xml index bffcb9b4f..b1f4b9ccb 100644 --- a/docs/en/xml/installation.xml +++ b/docs/en/xml/installation.xml @@ -1494,7 +1494,7 @@ c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s <para>What good are bugs if they're not annoying? To help make them more so you can set up Bugzilla's automatic whining system to complain at engineers - which leave their bugs in the NEW or REOPENED state without triaging them. + which leave their bugs in the CONFIRMED state without triaging them. </para> <para> This can be done by adding the following command as a daily |