Closed
Bug 183788
Opened 22 years ago
Closed 21 years ago
request mail auto-cc not working for original request
Categories
(Bugzilla :: Attachments & Requests, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: asa, Assigned: myk)
References
Details
Attachments
(1 file)
799 bytes,
patch
|
bbaetz
:
review+
|
Details | Diff | Splinter Review |
at bmo I have set up a flag, "approval1.3a", which is not specifically
requestable but is supposed to auto-cc drivers@mozilla.org and asa@mozilla.org.
The request approvals and denials (+ and -)send mail as expected but the
original request (?) does not auto-cc drivers@ and asa@.
Comment 1•22 years ago
|
||
I've actually noticed this w/attachment flags too. In this product our review
requests are supposed to cc reviewers@bugzilla.org but if you don't specify a
person, then the list doesn't get the message.
In fact, this is starting to sound like something I've typed before and it was
determined that this happens because if a person isn't specified, then there's
no message to cc the list to. Wonder if that was in a bug...
Comment 2•22 years ago
|
||
This must've just been talked about in IRC as I can't find any mention of it in
the few queries I ran.
Assignee | ||
Comment 3•21 years ago
|
||
Looks like the logic for whether to send an email erroneously required there to
be a requestee, which there isn't for requests which aren't specifically
requestable. This logic makes a requestee optional if there's a CC list.
Assignee | ||
Updated•21 years ago
|
Attachment #133992 -
Flags: review?(bbaetz)
Updated•21 years ago
|
Attachment #133992 -
Flags: review?(bbaetz) → review+
Assignee | ||
Comment 4•21 years ago
|
||
Checking in Bugzilla/Flag.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Flag.pm,v <-- Flag.pm
new revision: 1.14; previous revision: 1.13
done
Status: NEW → RESOLVED
Closed: 21 years ago
Flags: approval+
Resolution: --- → FIXED
Updated•21 years ago
|
Target Milestone: --- → Bugzilla 2.18
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•