Registry Admin does not have permission to delete teams

Bug #687676 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Curtis Hovey

Bug Description

The recent change to remove super teams before starting a merge breaks team deletions by the registry admins. The team does not have permission to call retractTeamMembership in many cases. There are two issues underlying this symptom.

1. The call to get super teams appears to be getting former or non-existent teams. retractTeamMembership() handles this case by returning early. This is good because many team owners clean up memberships before calling Delete. The doMerge() method could skip these cases but...

2. As with view code that prepares an object for deletion or merge, the case requires super privileges to complete the cleanup. Either Registry admins should have launchpad.Edit on the team, or gets special privileges on the method, or the view removed the security proxy to complete the task.

Related branches

Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
Changed in launchpad-registry:
assignee: nobody → Curtis Hovey (sinzui)
milestone: series-future → none
tags: added: qa-needstesting
Changed in launchpad-registry:
status: Triaged → Fix Committed
Curtis Hovey (sinzui)
tags: added: bugjam2010 qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui)
Changed in launchpad:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
Changed in launchpad:
milestone: none → 11.01
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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