bug assignment permissions too restrictive

Bug #603281 reported by Brian Murray on 2010-07-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Deryck Hodge

Bug Description

Bug 511269 is about setting up malone so that only bug supervisors can assign bug reports to people other than themselves or teams of which they are a member.

The problem is that the implementation is too restrictive:

"UserCannotEditBugTaskAssignee: Regular users can assign and unassign only themselves and their teams. Only project onwers, bug supervisors, drivers and release managers can assign others."

Participation in a project should be as easy as possible and In the event that the project does not have a bug supervisor anyone should be able to assign a bug task to someone. Configuring it this way also requires less work for the project owner.

Related branches

Deryck Hodge (deryck) wrote :

I've added this to the bugs backlog on the Kanban board. We should fix this ASAP. In the meantime, projects can work around not being able to assign bugs by creating a bug supervisor team and assigning users to this team who should have the ability to assign others.

Changed in malone:
status: New → Triaged
importance: Undecided → High
Deryck Hodge (deryck) on 2010-07-20
tags: added: dhrb
Deryck Hodge (deryck) on 2010-08-25
Changed in malone:
status: Triaged → In Progress
assignee: nobody → Deryck Hodge (deryck)
Deryck Hodge (deryck) on 2010-08-25
Changed in malone:
milestone: none → 10.09
tags: added: qa-needstesting
Changed in malone:
status: In Progress → Fix Committed
Deryck Hodge (deryck) on 2010-09-07
tags: added: qa-ok
removed: qa-needstesting
tags: removed: dhrb
Curtis Hovey (sinzui) on 2010-09-09
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers