Bug 146734

Summary: Commenting on a bug not accepted,
Product: [Community] Bugzilla Reporter: Horst H. von Brand <vonbrand>
Component: Bugzilla GeneralAssignee: David Lawrence <dkl>
Status: CLOSED CURRENTRELEASE QA Contact: Mike MacKenzie <mmackenz>
Severity: high Docs Contact:
Priority: medium    
Version: 2.18CC: fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-03-11 18:01:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Horst H. von Brand 2005-02-01 02:53:42 UTC
Description of problem:
Trying to comment on a previous bug via

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Go to beta bugzilla, log in, select bug 132495
2. Add a comment, go to second "Save changes" 
3. 
  
Actual results:
Complaint on trying to change asignee to "nobody" (?) without having required
empowerment. Going back and trying to save via first "Save changes" gives the
same result from then on

Expected results:
Save changes (comment), no complaint as nothing else was changed.

Additional info:
I'd prefer just one "Save changes" button, having two is confusing.

Comment 1 Thorsten Leemhuis 2005-02-23 08:06:10 UTC
This also sometimes (every time? -- not sure) happend to me when I type a
comment and try to submit it before I was logged in. The login-screen pops up,
and after that (when normaly "Changes are submitted" should come up) I get:

"
Not allowed
You tried to change the Assignee field from dkl to no value, but only
the owner or submitter of the bug, or a sufficiently empowered user, may change
that field.

Please press Back and try again.
"

Just happend again when I typed this bug. Need to open a new tab and paste the
comment there. Then submitting is no problem.

32bit firefox-0.10.1-1.0PR1.20 on x86_64 with several extensions (wild guess:
maybe the Tabbrowser-Extensions are the root of problem?)

Comment 2 David Lawrence 2005-03-11 18:01:02 UTC
This should be fixed now. Please reopen if not the case.

Comment 3 Thorsten Leemhuis 2005-03-13 14:36:19 UTC
(In reply to comment #2)
> This should be fixed now. 

Not fixed -- At least while I tried to add a "thanks for fixing" to this bug I got:

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

Please press Back and try again.
-------

> Please reopen if not the case.

Seems I can't (i was not the submitter of the bug)