253303 - Bug 42578 in buzilla.mozilla.org database cannot be modified.

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: General, defect)

Description

[Joseph R. Kiniry]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040614 Firefox/0.9

I have attempted to modify this bug from my Bugzilla.mozilla.org account using
several different web browsers and each time I try I get an error message.  I
suspect the database record for this bug is foobared.

Reproducible: Always
Steps to Reproduce:
1. Login to Bugzilla.mozilla.org
2. Go to http://bugzilla.mozilla.org/show_bug.cgi?id=42578
3. Try to add a CC and a comment.

Actual Results:  
Bugzilla responds with:

Not allowed
	  	
You tried to change the OS field from to All, but only the owner or submitter of
the bug, or a sufficiently empowered user, may change that field.

Please press Back and try again.

---

Of course, I did *not* change any other fields of the record.

Expected Results:  
It should commit the bug update.

Comment 1

[Bernard Alleysson]

WFM Firefox 0.9.1+ 20040726 Windows

Comment 2

[Simon Paquet [:sipaq]]

You need the appropriate permissions to change a bug.

See http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html

-> INVALID

Comment 3

[Joseph R. Kiniry]

How does one know if one has appropriate permissions to modify a bug (e.g., add
oneself as a CC)?  This is something I do frequently in many other bugzilla
installs.

I just tried this action again and it *worked* for me, so your claim of a
permission issue seems to be erroneous.

Comment 4

[Dave Miller [:justdave]]

You do need permissions to change most fields on a bug.  You can tell if you
have these permissions or not by visiting the Permissions tab in your user
preferences (click Prefs in the bugzilla footer).

You do not need permissions to add comments or CCs.

This bug was quite valid because they were getting an error saying that they had
changed the OS field, when in fact, they hadn't.

The real error that would have caused this would have been corruption in the
database, most likely that the OS field was null, which means the drop-down menu
would have been set the default value when you loaded the form.  Someone with
editbugs permissions would be able to do *anything* to the bug, and it would
have fixed this.  And it looks like someone already has.

The cause of the database corruption would have very likely been a system
administrator attempting to change the OS definitions without ensuring that the
names he was removing from the list weren't actually in use.