Closed
Bug 310259
Opened 19 years ago
Closed 19 years ago
submitter / reporter cannot change status from UNCONFIRMED to NEW
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 218771
People
(Reporter: bug, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.7.10) Gecko/20050715 Firefox/1.0.6 SUSE/1.0.6-4.3 Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.7.10) Gecko/20050715 Firefox/1.0.6 SUSE/1.0.6-4.3 the bug I reported has been confirmed by other users and assigned to someone. However, the status is still UNCONFIRMED. When trying to change this, I received the following error message: "You tried to change the Status field from UNCONFIRMED to NEW, but only the owner or submitter of the bug, or a sufficiently empowered user, may change that field" I am the "Reporter" (see url). I guess "Reporter" and "submitter" are a synonym (in which case it is a bug to use two terms to cause confusion). Reproducible: Always Steps to Reproduce: 1. check radio box to confirm bug 2. commit Actual Results: "You tried to change the Status field from UNCONFIRMED to NEW, but only the owner or submitter of the bug, or a sufficiently empowered user, may change that field" Expected Results: status changed to NEW (as I really _am_ the reporter) Additionally, after a few trials, the status change radio button list changed. Now I don't see "confirm bug" anymore. When selecting: "Reassign bug to owner and QA contact of selected component", the same message appears. (another confusing term is: "owner". I guess it's the assignee, but then again, why would I need to reassign a bug to the assignee...)
Comment 1•19 years ago
|
||
I believe this is either a dup, or just a problem with the error message. bmo is running pretty old code, at this point, so I think we've fixed this... haven't we?
OS: Linux → All
Hardware: PC → All
Version: unspecified → 2.19.1
(In reply to comment #1) do you mean to say that the behaviour is correct? The reporter should not be able to set the status from unconfirmed to new? Ok, after more STFW, I conclude: Bugzilla seems not to specify permissions (who can change what). It seems to be a matter of configuring the actual Bugzilla server. This fact should be documented in the Bugzilla documentation, for it is not clear even after some use (I'm not even sure whether or not my conclusion is valud). Therefore, I filed a bugreport to Bugzilla about it (Bug #310400) Here (on bugzilla.mozilla.org), the permission policies should be: 1) Specified (and explained) somewhere (see bug #179944) 2) Error messages should conform to this specification (this bug, I made it depend on bug #179944.)
Depends on: 179944
Comment 3•19 years ago
|
||
(In reply to comment #2) > do you mean to say that the behaviour is correct? The reporter should not be > able to set the status from unconfirmed to new? Correct! You need special privs to confirm a bug, even if you reported the bug (else everybody could open a bug and confirm it even if the bug is invalid). *** This bug has been marked as a duplicate of 218771 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
No longer depends on: 179944
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•