Closed Bug 179334 Opened 23 years ago Closed 23 years ago

removing + from a flag doesn't clear setter

Categories

(Bugzilla :: Attachments & Requests, defect)

2.17.1
x86
Linux
defect
Not set
major

Tracking

()

RESOLVED FIXED
Bugzilla 2.18

People

(Reporter: bbaetz, Assigned: myk)

References

Details

(Keywords: regression)

Attachments

(1 file, 3 obsolete files)

I wanted to get a= for my patch for bug 179321. joel had already ticked both review boxes, so I moved the + to a ?, and entered justdave's name in the box. The + did change to a ?, but joel's name ('bugreport') stayed as having set the flag, and I can't get justdave's name into the bracketed bit. The second thing may be related to the fact that you cant request a flag from noone, and then add a name to request it from someone specific 'regression' in new feature.
Attached patch patch v1: fixes problem (obsolete) — Splinter Review
Ok, this patch fixes the problem and also addresses: 1. requestee fields for both new and existing flags were called "requestee-xxx", where xxx was the ID of the flag's type. This doesn't work with multiplicable flag types, so I changed the requestee field names to "requestee_type-xxx" for new flags and "requestee-yyy", where yyy is the ID of the flag itself, for existing flags. 2. The name of the requestee was lost when existing flags were re-requested. 3. There was some unnecessary extra validation code in Flag.pm that validated requestee fields that we had already validated.
Attached patch patch v2 (obsolete) — Splinter Review
This patch also adds a fix for bug 179236, which is best fixed together with this bug since they are modifying the same code. interdiff to see the specific fix.
Attachment #105813 - Attachment is obsolete: true
Blocks: 179236
Attached patch patch v3 (obsolete) — Splinter Review
Fixes additional problems, like the inability to change the requestee for a requested flag.
Attachment #105817 - Attachment is obsolete: true
More updates to fix a variety of bugs and implement some features.
Attachment #105821 - Attachment is obsolete: true
Comment on attachment 105824 [details] [diff] [review] patch v4: more updates >@@ -473,11 +502,11 @@ > &::ThrowTemplateError($::template->error()); > } > >- my $delivery_mode = Param("sendmailnow") ? "" : "-ODeliveryMode=deferred"; >- open(SENDMAIL, "|/usr/lib/sendmail $delivery_mode -t -i") >- || die "Can't open sendmail"; >- print SENDMAIL $message; >- close(SENDMAIL); >+# my $delivery_mode = Param("sendmailnow") ? "" : "-ODeliveryMode=deferred"; >+# open(SENDMAIL, "|/usr/lib/sendmail $delivery_mode -t -i") >+# || die "Can't open sendmail"; >+# print SENDMAIL $message; >+# close(SENDMAIL); > } > Drop that hunk, and r=bbaetz. It seems to work on the test installation, but I'm sure someone will find a bug of some sort... ;)
Attachment #105824 - Flags: review+
a=myk Checking in attachment.cgi; /cvsroot/mozilla/webtools/bugzilla/attachment.cgi,v <-- attachment.cgi new revision: 1.31; previous revision: 1.30 done Checking in process_bug.cgi; /cvsroot/mozilla/webtools/bugzilla/process_bug.cgi,v <-- process_bug.cgi new revision: 1.166; previous revision: 1.165 done Checking in Bugzilla/Flag.pm; /cvsroot/mozilla/webtools/bugzilla/Bugzilla/Flag.pm,v <-- Flag.pm new revision: 1.4; previous revision: 1.3 done Checking in Bugzilla/User.pm; /cvsroot/mozilla/webtools/bugzilla/Bugzilla/User.pm,v <-- User.pm new revision: 1.8; previous revision: 1.7 done Checking in template/en/default/flag/list.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/flag/list.html.tmpl,v <-- list.html.tmpl new revision: 1.6; previous revision: 1.5 done
Status: NEW → RESOLVED
Closed: 23 years ago
Keywords: regression
Resolution: --- → FIXED
Blocks: 179284
Target Milestone: --- → Bugzilla 2.18
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: