The default bug view has changed. See this FAQ.

Restrict setting bug priority to assignees, triage leads, and module owners on a product basis

NEW
Unassigned

Status

()

bugzilla.mozilla.org
Bug Creation/Editing
--
enhancement
16 years ago
4 months ago

People

(Reporter: Stephen Rasku, Unassigned)

Tracking

({bmo-bug-quality})

Production
bmo-bug-quality

Details

(Whiteboard: [permissions:edit])

(Reporter)

Description

16 years ago
The way I see it, only the bug owner or the owner's manager (i.e. Someone with
the appropriate permissions) should be able to change priorities.  Even the
reporter shouldn't be able to set the priority a bug is at.
(Reporter)

Comment 1

16 years ago
Setting to P1 to prove my point.
Priority: -- → P1
Target Milestone: --- → Future
Traditionally Bugzilla has mostly allowed anyone to do anything.  Fixing that
general problem to the satisfaction of a whole range of system is a difficult
problem.
Severity: normal → enhancement
Priority: P1 → P3

Comment 3

16 years ago
-> Bugzilla product, Changing Bugs component, reassigning.
Assignee: tara → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Whiteboard: [permissions:edit]
Version: Bugzilla 2.12 → 2.12

Updated

14 years ago
OS: Solaris → All
Hardware: Sun → All

Updated

13 years ago
Depends on: 90619

Comment 4

13 years ago
The eclipse.org team would also like to see this enhancement.

As submitted by one of our committers:
Bug priorities are used by committers for planning purposes. They should not be
changed by submitters, which should use the severity field instead. It would be
great if there was a way to prevent less priviledged users from changing the
priority field. Since Bugzilla does not prevent them from doing it, it is a very
common mistake users make.

Updated

11 years ago
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Future → ---

Updated

10 years ago
Assignee: myk → create-and-change

Comment 5

6 years ago
Just to leave a link (although I don't hope much in the bright future for this bug) ... Red Hat bugzilla would welcome this as well. https://bugzilla.redhat.com/show_bug.cgi?id=456697

Comment 6

5 years ago
There is a patch in https://bugzilla.redhat.com/show_bug.cgi?id=495985#c24 which allows only a specific group to change priority/severity.
Might be worth to clean up and pick up, as I see such issues with non-dev reporters all over the place in the several Bugzillas that I triage in (bugzilla.mozilla.org being one of them) and this wastes a lot of time for developers getting tainted results when querying for high priority tickets.
CC'ing David as he is the downstream author.


(In reply to Matej Cepl from comment #5)
> https://bugzilla.redhat.com/show_bug.cgi?id=456697

"You are not authorized to access bug #456697." :)

Comment 7

3 years ago
Given the split nature of this bug, this may be better suited as an extension to Bugzilla.
Assignee: create-and-change → extension.ideas
Component: Creating/Changing Bugs → Extension Ideas
We say in https://bugzilla.mozilla.org/page.cgi?id=etiquette.html that changing priority unless you're a person working the bug or responsible for making decisions about priority is not allowed. It'd be nice to just implement that part of the CoC.

Given this bugs been quiet in the bugzilla component since 2014, I'm moving it to bmo.
Assignee: extension.ideas → nobody
Component: Extension Ideas → Bug Creation/Editing
Priority: P3 → --
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Summary: Anyone can change priority → Restrict setting bug priority to assignees, triage leads, and module owners on a product basis
Version: 2.12 → Production
No longer depends on: 90619
See Also: → bug 1310873
Keywords: bug-quality
You need to log in before you can comment on or make changes to this bug.