Bug 253340 - submitter can't close his own bugs even if assigned as the owner
submitter can't close his own bugs even if assigned as the owner
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs (Show other bugs)
All Linux
low Severity low (vote)
: ---
: ---
Assigned To: PnT DevOps Devs
Depends On:
  Show dependency treegraph
Reported: 2007-08-17 18:34 EDT by Arenas Belon, Carlo Marcelo
Modified: 2013-06-23 22:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-09-04 12:06:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Arenas Belon, Carlo Marcelo 2007-08-17 18:34:03 EDT
Description of problem:
while trying to close BUG253282 which I originally submitted as
Resolution=NOTABUG, I keep getting an error that says :

You tried to change the Status field from NEW to CLOSED, but only the owner or
submitter of the bug, or a autorized user, may change that field

changing the owner to my email account works, but doesn't work either.

How reproducible:

Steps to Reproduce:
1. log as a generic, not priviledged user
2. create a bug
3. try to close it
Actual results:
"not allowed" message

Expected results:
bug gets closed
Comment 1 Arenas Belon, Carlo Marcelo 2007-08-17 18:34:52 EDT
similar in concept to BUG192180 except that in that case the resolution was
"CLOSED: duplicate"
Comment 2 David Lawrence 2007-09-04 12:06:41 EDT
Unfortunately process/policy dictates that for certain bug reports (mostly RHEL
products), only Red Hat developers may close the bug completely. In the future
please add comment to the report asking that a bug be closed if it is invalid or

Note You need to log in before you can comment on or make changes to this bug.