Bug 147923

Summary:	I can't post a comment
Product:	[Community] Bugzilla	Reporter:	William M. Quarles <walrus>
Component:	Bugzilla General	Assignee:	Web Development <webdev>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Web Development <webdev>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0	CC:	dkl, lmeyer
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	https://bugzilla.redhat.com/beta/show_bug.cgi?id=134235
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-16 06:09:36 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 William M. Quarles 2005-02-13 00:17:18 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217

Description of problem:
I attempted to post a comment to the bug cited above.  I left the radio button on "Leave assigned to Adrian Likins."  Yet when I tried to submit my comment, I received this:

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

Something is wrong with this new version of Bugzilla.  I'm using the official Mozilla Suite release 1.7.5 for GNU/Linux.

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


How reproducible:
Always

Steps to Reproduce:
1.Type in some "Additional Comments"
2.Click the "Save Changes" button
3.Get the error message.
  

Actual Results:  Ugly red error message previously entered

Expected Results:  The comments should have been submitted and the bug should have been updated.

Additional info:

Comment 1 William M. Quarles 2005-02-13 00:25:06 UTC

Alright, this got laid out differently than I expected.  Just look at the URL
entered, or if you prefer bug #134235 is where it happened.  Just to note that
the bug had the status of NEW when I posted on it... if it gets assigned the
error might no longer be present, which means that it won't get fixed.

Comment 2 David Lawrence 2005-03-16 06:09:36 UTC

The unattended changing of assignee bug should be fixed now. Thanks.