Closed
Bug 212017
Opened 22 years ago
Closed 21 years ago
Unable to change a bug if it has a flag requested that is no longer requestable
Categories
(Bugzilla :: Attachments & Requests, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: justdave, Assigned: LpSolit)
References
Details
Attachments
(2 files)
|
1.91 KB,
patch
|
myk
:
review+
|
Details | Diff | Splinter Review |
|
1.91 KB,
patch
|
goobix
:
review+
|
Details | Diff | Splinter Review |
I tried to add myself to the CC on bug 192425, which had "blocking 1.4" set to
"?". blocking 1.4 has since been disabled (and has the "requestable" flag
cleared as well). It would not let me add myself to the CC because it
complained that "?" wasn't a legal setting for that flag.
Bugzilla has suffered an internal error. Please save this page and send it to
myk@mozilla.org with details of what you were doing at the time this message
appeared.
URL: http://bugzilla.mozilla.org/process_bug.cgi
The flag status ? is invalid.
Variables:
status: ?
id: 42101
| Reporter | ||
Updated•22 years ago
|
Version: 2.17.4 → 2.17.1
| Reporter | ||
Comment 1•22 years ago
|
||
Asa/Ian: the reason you guys got copied:
The following link displays the list of bugs that users can no longer make
changes to because of this bug.
http://bugzilla.mozilla.org/request.cgi?action=queue&type=blocking1.4&group=type
Someone needs to either clear/grant/deny the "blocking 1.4" flag on all of those
bugs before anyone will be able to make changes to them again.
Comment 2•22 years ago
|
||
I've added back "requestability" to that flag on b.m.o so changes won't fail
anymore.
Updated•22 years ago
|
Blocks: rt-clean-up
| Assignee | ||
Updated•21 years ago
|
Assignee: myk → LpSolit
Status: ASSIGNED → NEW
| Assignee | ||
Updated•21 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 4•21 years ago
|
||
If a flag is requested before this flag type becomes unrequestable, "?" still
has to be displayed! The 2.18 branch and the trunk both actually display the
requester, I think also the requestee if any (didn't check this point), but the
"?" flag is not visible (i.e. is unavailable)! This doesn't make sense!! Even
worse, the activity log shows that "?" is still kept in the DB (it really is),
but if the user clicks "submit", this flag will definitively be deleted.
| Assignee | ||
Comment 5•21 years ago
|
||
Comment on attachment 163217 [details] [diff] [review]
Allows "?" if already set
myk, justdave, I think this should be included in 2.18 as well as in the trunk.
Attachment #163217 -
Flags: review?(myk)
| Assignee | ||
Updated•21 years ago
|
Flags: blocking2.20?
Flags: blocking2.18?
| Assignee | ||
Comment 6•21 years ago
|
||
This problem seems to exist since 2003-04-24 22:41 and the check-in of bug
179510 about the error message and since 2002-11-09 05:57 and the check-in of
bug 179205 about the UI.
Comment 7•21 years ago
|
||
Comment on attachment 163217 [details] [diff] [review]
Allows "?" if already set
Thanks, this is a great fix.
>+ # If the flag was requested before it became unrequestable, left it as is.
Nit: "left it as is" should be "leave it as is" for consistency in grammatical
tense between this comment and the others in this file.
r=myk
Attachment #163217 -
Flags: review?(myk) → review+
| Assignee | ||
Comment 8•21 years ago
|
||
As said in comment 5, this patch should also go into the 2.18 branch, IMHO.
Requesting approval...
Flags: approval?
Flags: approval2.18?
| Assignee | ||
Comment 9•21 years ago
|
||
Nit corrected: "left it as is" -> "leave it as is".
Comment 10•21 years ago
|
||
This is a good, low-risk correctness fix that it makes sense to get into our
impending releases.
Flags: blocking2.20?
Flags: blocking2.18?
Flags: approval?
Flags: approval2.18?
Flags: approval2.18+
Flags: approval+
Target Milestone: --- → Bugzilla 2.18
Updated•21 years ago
|
Attachment #163637 -
Flags: review+
Comment 11•21 years ago
|
||
Checking in Bugzilla/Flag.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Flag.pm,v <-- Flag.pm
new revision: 1.18.2.3; previous revision: 1.18.2.2
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.12.2.1; previous revision: 1.12
done
Checking in Bugzilla/Flag.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Flag.pm,v <-- Flag.pm
new revision: 1.22; previous revision: 1.21
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.14; previous revision: 1.13
done
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 12•21 years ago
|
||
*** Bug 251738 has been marked as a duplicate of this bug. ***
Updated•13 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
•