summaryrefslogtreecommitdiffstats
path: root/process_bug.cgi
diff options
context:
space:
mode:
authormyk%mozilla.org <>2003-04-25 14:41:20 +0200
committermyk%mozilla.org <>2003-04-25 14:41:20 +0200
commit47c010537c77f8e7e09e6c19246cdbecbb7b5a26 (patch)
tree515f996ddc173bcae29f0ede8f77de48d59bc6f4 /process_bug.cgi
parentadc665e91aa228734632e51cb42d671bbbab9f7f (diff)
downloadbugzilla-47c010537c77f8e7e09e6c19246cdbecbb7b5a26.tar.gz
bugzilla-47c010537c77f8e7e09e6c19246cdbecbb7b5a26.tar.xz
Fix for bug 179510: takes group restrictions into account when sending request notifications
r=bbaetz,jpreed a=justdave
Diffstat (limited to 'process_bug.cgi')
-rwxr-xr-xprocess_bug.cgi15
1 files changed, 14 insertions, 1 deletions
diff --git a/process_bug.cgi b/process_bug.cgi
index 09b45cf92..83d601d33 100755
--- a/process_bug.cgi
+++ b/process_bug.cgi
@@ -91,12 +91,21 @@ scalar(@idlist) || ThrowUserError("no_bugs_chosen");
# do a match on the fields if applicable
+# The order of these function calls is important, as both Flag::validate
+# and FlagType::validate assume User::match_field has ensured that the values
+# in the requestee fields are legitimate user email addresses.
&Bugzilla::User::match_field({
'qa_contact' => { 'type' => 'single' },
'newcc' => { 'type' => 'multi' },
'assigned_to' => { 'type' => 'single' },
'^requestee(_type)?-(\d+)$' => { 'type' => 'single' },
});
+# Validate flags, but only if the user is changing a single bug,
+# since the multi-change form doesn't include flag changes.
+if (defined $::FORM{'id'}) {
+ Bugzilla::Flag::validate(\%::FORM, $::FORM{'id'});
+ Bugzilla::FlagType::validate(\%::FORM, $::FORM{'id'});
+}
# If we are duping bugs, let's also make sure that we can change
# the original. This takes care of issue A on bug 96085.
@@ -1080,7 +1089,11 @@ foreach my $id (@idlist) {
"products READ, components READ, " .
"keywords $write, longdescs $write, fielddefs $write, " .
"bug_group_map $write, flags $write, duplicates $write," .
- "user_group_map READ, flagtypes READ, " .
+ # user_group_map would be a READ lock except that Flag::process
+ # may call Flag::notify, which calls ConfirmGroup, which might
+ # call DeriveGroup, which wants a WRITE lock on that table.
+ # group_group_map is in here at all because DeriveGroups needs it.
+ "user_group_map $write, group_group_map READ, flagtypes READ, " .
"flaginclusions AS i READ, flagexclusions AS e READ, " .
"keyworddefs READ, groups READ, attachments READ, " .
"group_control_map AS oldcontrolmap READ, " .