Launchpad itself

only bug supervisor should be able to assign bugs to other people

Bug #511269 reported by Brian Murray
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Abel Deuring
Launchpad itself 10.07

Bug Description

Currently, Ubuntu has an issue where people will assign bugs to teams or developers in the hope that this will get them fixed. However, it does not get them fixed and only ends up causing busy work for the team or developer. Subsequently, it would be useful if only the bug supervisor were able to assign bugs to individuals but people's ability to assign bug reports to the themselves was preserved.

To make this more generic for other projects the project could be checked to see if it has a bug supervisor and in the event that it does the same rule (only bug supervisors can assign bug reports to others) would apply.

Tags: lp-bugs qa-ok

Related branches

lp://staging/~adeuring/launchpad/bug-511269
Graham Binns (community): Approve (code)
Diff: 1950 lines (+679/-892)
20 files modified
lib/canonical/launchpad/javascript/bugs/bugtask-index.js (+18/-4)
lib/canonical/launchpad/scripts/sftracker.py (+0/-448)
lib/canonical/launchpad/scripts/tests/test_sftracker.py (+0/-347)
lib/canonical/launchpad/templates/bugtask-assignee-widget.pt (+2/-2)
lib/canonical/widgets/bugtask.py (+23/-0)
lib/lp/bugs/browser/bugtask.py (+20/-2)
lib/lp/bugs/browser/tests/test_bugtask.py (+30/-0)
lib/lp/bugs/configure.zcml (+3/-1)
lib/lp/bugs/doc/bugtask.txt (+74/-0)
lib/lp/bugs/interfaces/bugtask.py (+25/-0)
lib/lp/bugs/model/bugtask.py (+45/-2)
lib/lp/bugs/scripts/bugzilla.py (+12/-7)
lib/lp/bugs/stories/bugtask-management/xx-change-assignee.txt (+87/-4)
lib/lp/bugs/tests/bugs-emailinterface.txt (+8/-7)
lib/lp/bugs/tests/test_bugtask.py (+226/-2)
lib/lp/coop/answersbugs/tests/notifications-linked-bug.txt (+2/-0)
lib/lp/registry/tests/test_user_vocabularies.py (+69/-2)
lib/lp/registry/vocabularies.py (+22/-0)
lib/lp/registry/vocabularies.zcml (+13/-0)
scripts/sourceforge-import.py (+0/-64)
Revision history for this message
Daniel Stone (danielstone) wrote :

When a team or project has no contact (bug supervisor)
What would be done at that point.?

Revision history for this message
Brian Murray (brian-murray) wrote :

Right, sorry.

In the event that the project has no bug supervisor anyone can assign bug reports to people.

Revision history for this message
Curtis Hovey (sinzui) wrote :

A driver and certainly the release manager must have permission to assign bugs to people. I think users who are not a role for a project should be permitted to assign the bug to themselves or their teams.

Changed in malone:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Daniel Stone (danielstone) wrote :

Only on projects without a bug supervisor should members be allowed to assogn. In my eyes that is the role of the project owner to assign a bug spervisor to manage such issues.
On projects that do not have that role filled the project owner should have the auth to change and assign/appoint someone should the need be.

Revision history for this message
C de-Avillez (hggdh2) wrote :

FWIW, I agree with the following rephrase: only the package bug supervisor can assign *others* to the bug. Anyone can still self-assign to a bug. If no bug supervisor exists for the package, anyone can *self-assign*.

One of the things we want to encourage is community participation, and closing this would hurt it.

Deryck Hodge (deryck)
Changed in malone:
assignee: nobody → Abel Deuring (adeuring)
status: Triaged → In Progress
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit

Fixed in stable r10943 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/10943>

Changed in malone:
milestone: none → 10.06
status: In Progress → Fix Committed
tags: added: qa-needstesting
Deryck Hodge (deryck)
tags: added: qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui)
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.