- Back to bug [% bug_id %] + Back to [% terms.bug %] [% bug_id %]
[% PROCESS global/footer.html.tmpl %] diff --git a/template/en/default/bug/activity/table.html.tmpl b/template/en/default/bug/activity/table.html.tmpl index 95beaef14..ec005cc38 100644 --- a/template/en/default/bug/activity/table.html.tmpl +++ b/template/en/default/bug/activity/table.html.tmpl @@ -23,7 +23,7 @@ # operations: array of hashes. May be empty. Each has has three members: # who: string. who performed the operation # when: string. when they performed it - # changes: hash. Details of what they changed. This hash has three + # changes: hash. Details of what they changed. This hash has three # compulsory and one optional member: # field: string. The name of the field # removed: string. What was removed from the field @@ -33,14 +33,16 @@ # it was affected by an old Bugzilla bug.) #%] +[% PROCESS global/variables.none.tmpl %] + [% PROCESS bug/time.html.tmpl %] - + [% IF incomplete_data %]- There used to be a bug Bugzilla which caused activity data + There used to be a [% terms.bug %] in [% terms.Bugzilla %] which caused activity data to be lost if there was a large number of cc's or dependencies. That - has been fixed, however, there was some data already lost on this bug - that could not be regenerated. The changes that the script could not + has been fixed, however, there was some data already lost on this [% terms.bug %] that + could not be regenerated. The changes that the script could not reliably determine are prefixed by '?'.
[% END %] @@ -55,7 +57,7 @@- This is a template used on mozilla.org - it, along with the + This is a template used on mozilla.org - it, along with the comment-guided.txt.tmpl template, are included as a demo of what it's - possible to do with custom templates in general, and custom bug entry + possible to do with custom templates in general, and custom [% terms.bug %] entry templates in particular. It is recommended that this template be - customised if you want to use it on your Bugzilla installation. + customised if you want to use it on your [% terms.Bugzilla %] installation.
@@ -66,15 +68,15 @@ function PutDescription() { [%# Browser sniff to try and reduce the incidence of 4.x and NS 6/7 bugs %] [% IF cgi.user_agent("Mozilla/4") AND NOT cgi.user_agent("compatible") %] -This form prompts you for the information required to - file a good bug report (or enhancement request.) - It may seem lengthy, but developers need all this information - to understand and reproduce the bug, which is the first step towards - fixing it. Please note that we do not accept bug reports by - email - please do not email developers or mozilla.org staff - with bug reports. Also, please do not - file Mozilla bugs on copies of Mozilla older than two weeks - first, - download a + file a good [% terms.bug %] report (or enhancement request.) + It may seem lengthy, but developers need all this information + to understand and reproduce the [% terms.bug %], which is the first step towards + fixing it. Please note that we do not accept [% terms.bug %] reports by + email - please do not email developers or mozilla.org staff + with [% terms.bug %] reports. Also, please do not + file Mozilla [% terms.bugs %] on copies of Mozilla older than two weeks - first, + download a newer build and check that the problem is still present.
- -- You need to see if your bug has already been reported. - Please don't skip this step. - 50% of the bugs filed in - Bugzilla are duplicates, and and this wastes a lot of our QA engineers' time. + You need to see if your [% terms.bug %] has already been reported. + Please don't skip this step. + 50% of the [% terms.bugs %] filed in + [% terms.Bugzilla %] are duplicates, and and this wastes a lot of our QA engineers' time.
[%# Stop NS 4.x and all v.3 browsers from getting @@ -181,41 +183,41 @@ function PutDescription() {Look through the search results. If you get the - Zarro Boogs message, Bugzilla found no bugs that + Zarro Boogs message, [% terms.Bugzilla %] found no [% terms.bugs %] that match. Check for typos, or add fewer or different keywords.
- If you find a bug that looks the same as yours, you can add - useful comments to that bug, but please don't open a new one. - Please don't add comments like "please fix this bug" - this + If you find [% terms.abug %] that looks the same as yours, you can add + useful comments to that [% terms.bug %], but please don't open a new one. + Please don't add comments like "please fix this [% terms.bug %]" - this tends to annoy engineers and slow, rather than speed, the fixing of it.
- If you find bugs similar to yours, read them and note which component - they are in. You should file your bug in that same component. + If you find [% terms.bugs %] similar to yours, read them and note which component + they are in. You should file your [% terms.bug %] in that same component.
- +- If you're pretty certain that your bug isn't in there already, then + If you're pretty certain that your [% terms.bug %] isn't in there already, then please try to complete this form as accurately as you can. The more you can tell us, the better our chance of being able - to understand and reproduce your bug. + to understand and reproduce your [% terms.bug %].
-