Closed Bug 96487 Opened 24 years ago Closed 19 years ago

case problem with keywords

Categories

(Bugzilla :: Creating/Changing Bugs, defect, P3)

Product:
Bugzilla
Component:
Creating/Changing Bugs
Version:
2.13
Platform:
All
Other
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: nine, Unassigned)

Details

I wanted to comment on a bug with the nsBranch keyword. When submitting I got an error message about only someone with sufficient rights may change the keyword field but I didn't change it. It complained about the old value was "nsBranch" and the new "nsbranch" wich is what bugzilla wrote in the keyword field.
The root cause of this is bug #69621, but I'm thinking we should try to be robust with this. Even once that is fixed problems could occur - if the keyword cache of a bug got out of whack we could let a user fix the cache even if they don't have permission. Or is this a good thing, in that it would let people know about cache corruption?
Severity: minor → normal
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
Moving to new Bugzilla product ...
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: Bugzilla 2.10 → 2.13
Really reassigning ...
Assignee: justdave → myk
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
These unloved bugs have been sitting untouched since June 2002 or longer. If nobody does anything else to them, they certainly won't make 2.18 Retargetting to 2.20. If you really plan to push them right now, you might pull them back in.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---
*** Bug 252004 has been marked as a duplicate of this bug. ***
this works in 2.20+
Flags: approval?
Flags: approval?
QA Contact: mattyt-bugzilla → default-qa
Assignee: myk → create-and-change
This won't get fixed on branches < 2.20 So is it a WORKSFORME or WONTFIX... I donno. I'm sure I'll guess wrong.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Yeah, if it works now it's WORKSFORME. :-)
Resolution: WONTFIX → WORKSFORME
Any idea what fixed it? Did the UTF8-ification change the default string comparison rues or something else?
You need to log in before you can comment on or make changes to this bug.