From df89108542a59e1a3a3ccf2cdcab61407989bd46 Mon Sep 17 00:00:00 2001 From: "gerv%gerv.net" <> Date: Tue, 10 May 2005 05:49:41 +0000 Subject: Bug 215148 - make status and resolution localisable. Patch by eseyman@linagora.com; r=gerv, a=myk. --- template/en/default/pages/fields.html.tmpl | 59 +++++++++++++++--------------- 1 file changed, 30 insertions(+), 29 deletions(-) (limited to 'template/en/default/pages') diff --git a/template/en/default/pages/fields.html.tmpl b/template/en/default/pages/fields.html.tmpl index a1224f600..fb1c95e26 100644 --- a/template/en/default/pages/fields.html.tmpl +++ b/template/en/default/pages/fields.html.tmpl @@ -21,6 +21,7 @@ #%] [% PROCESS global/variables.none.tmpl %] +[% PROCESS "global/field-descs.none.tmpl" %] [% INCLUDE global/header.html.tmpl title = "A $terms.Bug's Life Cycle" %]

@@ -54,45 +55,45 @@ cycle of [% terms.abug %].

- UNCONFIRMED + [% status_descs.UNCONFIRMED FILTER html %]
This [% terms.bug %] has recently been added to the database. Nobody has validated that this [% terms.bug %] is true. Users who have the "canconfirm" permission set may confirm - this [% terms.bug %], changing its state to NEW. Or, it may be - directly resolved and marked RESOLVED. + this [% terms.bug %], changing its state to [% status_descs.NEW FILTER html %]. Or, it may be + directly resolved and marked [% status_descs.RESOLVED FILTER html %].
- NEW + [% status_descs.NEW FILTER html %]
This [% terms.bug %] has recently been added to the assignee's list of [% terms.bugs %] and must be processed. [% terms.Bugs %] in - this state may be accepted, and become ASSIGNED, passed - on to someone else, and remain NEW, or resolved and marked - RESOLVED. + this state may be accepted, and become [% status_descs.ASSIGNED FILTER html %], passed + on to someone else, and remain [% status_descs.NEW FILTER html %], or resolved and marked + [% status_descs.RESOLVED FILTER html %].
- ASSIGNED + [% status_descs.ASSIGNED FILTER html %]
This [% terms.bug %] is not yet resolved, but is assigned to the proper person. From here [% terms.bugs %] can be given to another - person and become NEW, or resolved and become RESOLVED. + person and become [% status_descs.NEW FILTER html %], or resolved and become [% descs.bug_status_descs.RESOLVED FILTER html %].
- REOPENED + [% status_descs.REOPENED FILTER html %]
This [% terms.bug %] was once resolved, but the resolution was - deemed incorrect. For example, a WORKSFORME [% terms.bug %] is - REOPENED when more information shows up and + deemed incorrect. For example, a [% status_descs.WORKSFORME FILTER html %] [% terms.bug %] is + [% status_descs.REOPENED FILTER html %] when more information shows up and the [% terms.bug %] is now reproducible. From here [% terms.bugs %] are - either marked ASSIGNED or RESOLVED. + either marked [% status_descs.ASSIGNED FILTER html %] or [% descs.bug_status_descs.RESOLVED FILTER html %].
@@ -113,33 +114,33 @@ cycle of [% terms.abug %].
- RESOLVED + [% status_descs.RESOLVED FILTER html %]
A resolution has been taken, and it is awaiting verification by QA. From here [% terms.bugs %] are either re-opened and become - REOPENED, are marked VERIFIED, or are closed for - good and marked CLOSED. + [% status_descs.REOPENED FILTER html %], are marked [% descs.bug_status_descs.VERIFIED FILTER html %], or are closed for + good and marked [% status_descs.CLOSED FILTER html %].
- VERIFIED + [% status_descs.VERIFIED FILTER html %]
QA has looked at the [% terms.bug %] and the resolution and agrees that the appropriate resolution has been taken. [% terms.Bugs %] remain in this state until the product they were reported against actually ships, at which point they become - CLOSED. + [% status_descs.CLOSED FILTER html %].
- CLOSED + [% status_descs.CLOSED FILTER html %]
The [% terms.bug %] is considered dead, the resolution is correct. Any zombie [% terms.bugs %] who choose to walk the earth again must - do so by becoming REOPENED. + do so by becoming [% status_descs.REOPENED FILTER html %].
@@ -147,7 +148,7 @@ cycle of [% terms.abug %].
- FIXED + [% resolution_descs.FIXED FILTER html %]
A fix for this [% terms.bug %] is checked into the tree and @@ -155,14 +156,14 @@ cycle of [% terms.abug %].
- INVALID + [% resolution_descs.INVALID FILTER html %]
The problem described is not [% terms.abug %].
- WONTFIX + [% resolution_descs.WONTFIX FILTER html %]
The problem described is [% terms.abug %] which will never be @@ -170,7 +171,7 @@ cycle of [% terms.abug %].
- DUPLICATE + [% resolution_descs.DUPLICATE FILTER html %]
The problem is a duplicate of an existing [% terms.bug %]. @@ -180,7 +181,7 @@ cycle of [% terms.abug %].
- WORKSFORME + [% resolution_descs.WORKSFORME FILTER html %]
All attempts at reproducing this [% terms.bug %] were futile, @@ -190,7 +191,7 @@ cycle of [% terms.abug %].
- MOVED + [% resolution_descs.MOVED FILTER html %]
The problem was specific to a related product @@ -295,12 +296,12 @@ others.

This is the person in charge of resolving the [% terms.bug %]. Every time -this field changes, the status changes to NEW to make it +this field changes, the status changes to [% status_descs.NEW FILTER html %] to make it easy to see which new [% terms.bugs %] have appeared on a person's list.

-The default status for queries is set to NEW, ASSIGNED and -REOPENED. When searching for [% terms.bugs %] that have been resolved or +The default status for queries is set to [% status_descs.NEW FILTER html %], [% descs.bug_status_descs.ASSIGNED FILTER html %] and +[% status_descs.REOPENED FILTER html %]. When searching for [% terms.bugs %] that have been resolved or verified, remember to set the status field appropriately.

-- cgit v1.2.3-24-g4f1b