Open Bug 394248 Opened 17 years ago Updated 7 years ago

Add some readability to the flag mail template

Categories

(Bugzilla :: Attachments & Requests, defect)

3.1.1
defect
Not set
minor

Tracking

()

People

(Reporter: Wurblzap, Unassigned)

Details

Attachments

(1 file, 1 obsolete file)

Attached patch Patch (obsolete) — Splinter Review
As it is, I think the flag mail template is very confusing. It's tied tightly to English grammar, and it's rather difficult to follow its code paths and magic variables. This gives trouble to code contributors and localizers.

Attached is a first attempt to remedy this.
Attachment #278862 - Flags: review?(LpSolit)
I don't like these "own request" strings. This makes the logic so complicated. That's mostly a r- due to that. Most strings can be merged two by two.
Attached patch Patch 2Splinter Review
Ok, this is what both of us can live with probably.
Attachment #278862 - Attachment is obsolete: true
Attachment #280255 - Flags: review?(LpSolit)
Attachment #278862 - Flags: review?(LpSolit)
Comment on attachment 280255 [details] [diff] [review]
Patch 2

>+[% IF flag.status == '?' %]
>+  [%-# We're asking for somebody else's decision. %]
>+  [% IF ! flag.setter %]
>+    [%-# This question hasn't been asked before. %]

A flag always has a setter, so the IF test is wrong. It seems you meant [% IF flag.setter.id == user.id %], i.e. you want to know if you are reassigning the request or not (per what is written in the ELSE block).


>+    [% IF flag.requestee %]
>+      [%-# We're asking specifically. %]
>+      [% user.identity %] has [% body_activities.${flag.status} %] [%+ flag.requestee.identity %] for [% flag.type.name %]:
>+    [% ELSE %]
>+      [%-# We're asking the wind. %]
>+      [% user.identity %] has [% body_activities.${flag.status} %] for [% flag.type.name %]:
>+    [% END %]

All this code do is to remove the extra whitespace if no requestee is defined. I'm not sure it worths the ELSE block.



>+  [% ELSE %]
>+    [%-# This question has been asked before (reassignment). There is no
>+       # immediate need to special-case this, but it's friendlier to have a
>+       # dedicated message.
>+       #%]

Huh? Unless I miss something, this comment has nothing to do here.


>+    [%-# We're reassigning somebody else's request. %]
>+    [% user.identity %] has reassigned [% flag.setter.identity %]'s request for [% flag.type.name %] to [% flag.requestee.identity %]:

This doesn't work if there is no new requestee (request from the wind) as the sentence would end as "to ".


The rest of the code looks correct.
Attachment #280255 - Flags: review?(LpSolit) → review-
Too late for 3.2.
Target Milestone: Bugzilla 3.2 → Bugzilla 4.0
We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.
Target Milestone: Bugzilla 4.4 → ---
5 years down the road, this is WONTFIX as far as I'm concerned.
Assignee: wurblzap → attach-and-request
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: