Closed
Bug 1179503
Opened 10 years ago
Closed 10 years ago
Something weird with bug 1179068
Categories
(bugzilla.mozilla.org :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: glandium, Unassigned)
Details
See https://bugzilla.mozilla.org/show_bug.cgi?id=1179068#c1
Apparently, a "new to bugzilla" user was able to change a bunch of flags for some reasons, and AIUI, that shouldn't happen unless they have editbugs perms, which seems odd of a "new to bugzilla" user.
Relatedly, the bug history link that used to be in the classic theme is not there anymore, and that history used to be more reliable than the inline history, so I wanted to look at the full bug history, but couldn't find it (and relatedly, got surprised that the classic theme has nothing to do with what it was a few weeks ago)
Reporter | ||
Comment 1•10 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #0)
> Relatedly, the bug history link that used to be in the classic theme is not
> there anymore, and that history used to be more reliable than the inline
> history, so I wanted to look at the full bug history, but couldn't find it
> (and relatedly, got surprised that the classic theme has nothing to do with
> what it was a few weeks ago)
Ah, that's all because I have the experimental UI on, that alters even the classic theme in various ways. So in fact, I was able to get to the bug history which shows the same thing as the inline history.
reporters have the ability to change the values of most field on their own bugs (for better or worse), so this is working as designed.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 3•10 years ago
|
||
Should reporters with no editbugs perms be allowed to edit tracking flags?
(In reply to Mike Hommey [:glandium] from comment #3)
> Should reporters with no editbugs perms be allowed to edit tracking flags?
yes - they can _request_ and clear tracking flags (but not set them).
you need to be able to clear flags in order to revert flags you request.
You need to log in
before you can comment on or make changes to this bug.
Description
•