Closed
Bug 178157
Opened 22 years ago
Closed 19 years ago
Dependency emails don't get sent for status change during mass change
Categories
(Bugzilla :: Creating/Changing Bugs, defect, P1)
Bugzilla
Creating/Changing Bugs
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: bbaetz, Assigned: LpSolit)
Details
Attachments
(1 file, 1 obsolete file)
1.71 KB,
patch
|
myk
:
review+
|
Details | Diff | Splinter Review |
We send dependancy mails based on the incorrectly named 'dependencychanged' hash in process_bug. This seems to be reading from the form value, and then later ading any change values. For mass changes, the form value will be blank, and there will be no changes, so the hash is empy, and processmail isn't called on mass resolves. The info is sent the next time mail happens on the bug, for whatever reason. myk, is |processmail -rescanall| still being run semi-regularly?
Reporter | ||
Comment 1•22 years ago
|
||
(OK, its not really dataloss, since the mail will get send eventually. Its still Not Good)
Keywords: dataloss
Comment 2•22 years ago
|
||
Yes, it's run once a day early in the morning.
Comment 3•22 years ago
|
||
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss bugs are of critical or possibly higher severity. Only changing open bugs to minimize unnecessary spam. Keywords to trigger this would be crash, topcrash, topcrash+, zt4newcrash, dataloss.
Severity: major → critical
Updated•21 years ago
|
Summary: Dependancy emails don't get sent for status change during mass change → Dependency emails don't get sent for status change during mass change
Comment 4•21 years ago
|
||
bbaetz: do you know what the solution is here? Gerv
Updated•20 years ago
|
Flags: blocking2.20?
Flags: blocking2.18.1?
Updated•19 years ago
|
Flags: blocking2.20?
Keywords: dataloss
OS: Linux → All
Hardware: PC → All
Target Milestone: --- → Bugzilla 2.18
Updated•19 years ago
|
Flags: blocking2.20+
Flags: blocking2.18.1?
Flags: blocking2.18.1+
Updated•19 years ago
|
Assignee: myk → create-and-change
Priority: -- → P1
QA Contact: mattyt-bugzilla → default-qa
Assignee | ||
Comment 6•19 years ago
|
||
Taking! I know process_bug.cgi by heart now :)
Assignee: create-and-change → LpSolit
Assignee | ||
Comment 7•19 years ago
|
||
Applies to both 2.18 and the trunk. We now check for dependencies even if the corresponding fields are not available from the UI (which is the case when changing several bugs at once).
Attachment #177775 -
Flags: review?(myk)
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Comment 8•19 years ago
|
||
Comment on attachment 177775 [details] [diff] [review] patch, v1 Looks like it works, but the new looping code is hard to grok. I suggest not changing the original code or changing it to something a little easier to understand, f.e.: foreach my ($pair) = ("blocked/dependson", "dependson/blocked") { my ($source, $target) = split("/", $pair); ... }
Attachment #177775 -
Flags: review?(myk) → review+
Assignee | ||
Comment 9•19 years ago
|
||
Nit fixed!
Attachment #177775 -
Attachment is obsolete: true
Attachment #177797 -
Flags: review?(myk)
Updated•19 years ago
|
Attachment #177797 -
Flags: review?(myk) → review+
Updated•19 years ago
|
Flags: approval+
Assignee | ||
Updated•19 years ago
|
Flags: approval2.18?
Updated•19 years ago
|
Flags: approval2.18? → approval2.18+
Assignee | ||
Comment 10•19 years ago
|
||
Tip: Checking in process_bug.cgi; /cvsroot/mozilla/webtools/bugzilla/process_bug.cgi,v <-- process_bug.cgi new revision: 1.243; previous revision: 1.242 done 2.18 Branch: Checking in process_bug.cgi; /cvsroot/mozilla/webtools/bugzilla/process_bug.cgi,v <-- process_bug.cgi new revision: 1.205.2.16; previous revision: 1.205.2.15 done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•