Open
Bug 643264
Opened 14 years ago
Updated 10 years ago
Field values with "Enabled for bugs" disabled can be set anyway
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement)
Tracking
()
NEW
People
(Reporter: idl0r, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110308 Gentoo Firefox/3.6.15
Build Identifier:
A field value which has been set as "Disabled for bugs" can be set anyway via POST, even JSON/XML-RPC could be affected.
Reproducible: Always
Steps to Reproduce:
1. Disable a field value for bugs
2. On process_bug.cgi use e.g. "?resolution=<a disabled resolution>
Actual Results:
It still uses disabled field values
Expected Results:
It shouldn't allow disabled field values, it should rather throw an error
|
||
Comment 1•14 years ago
|
||
Thanks for your report. I believe this is a duplicate of an already-filed enhancement or bug, but I'm not sure. We are aware of this behavior, and were when we wrote the disabling code.
The trick here is to implement this in the backend such that if the value is *currently* a disabled value, that value can be "set" (meaning the field doesn't change) on this bug, but any other disabled value can *not* be set. I think that should work just fine.
Whiteboard: DUPME
|
||
Comment 2•14 years ago
|
||
I cannot find the dupe. So confirming!
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
Whiteboard: DUPME
Version: unspecified → 4.0
We're seeing that too... We've set Windows NT to enabled for bugs = "no", yet new bugs filed from a Windows 8.1 computer get assigned to Windows NT.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=460621
You need to log in
before you can comment on or make changes to this bug.
Description
•