Private branch owner cannot unsubscribe someone

Bug #283167 reported by Matthew Revell
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Ian Booth

Bug Description

Paolo Garbin reports:

"In a private branch (https://code.launchpad.net/~ubuntu-it-magazine/fcm-it/edizione-fcm-it ) the project-admin can't delete the subscriptions listed at the right.

In this list there are ex project-members, that now not active in our project. We want to remove them from this branch.

The private branch is: https://code.launchpad.net/~ubuntu-it-magazine/fcm-it/edizione-fcm-it"

Related branches

description: updated
description: updated
Revision history for this message
Tim Penhey (thumper) wrote :

This is correct.

The ex project-members will no longer be able to write to the team owned branch if they are no longer in the team, however their subscriptions are still valid. If there is a reason for them to not be allowed to see the branch any more, then a question on the launchpad (or launchpad-bazaar) project is needed to remove the branch subscriptions.

Changed in launchpad:
status: New → Won't Fix
Revision history for this message
Paolo Garbin (paolettopn) wrote :

Hi, Tim.

I understand now.

The branch admin add a request on launchpad, for remove the old members from our branch.

Revision history for this message
Paolo Garbin (paolettopn) wrote :

close this question

Changed in launchpad:
assignee: nobody → paolettopn
status: New → Confirmed
assignee: paolettopn → nobody
Changed in launchpad:
status: Confirmed → Invalid
tags: added: oem-services
Revision history for this message
Karl Fogel (kfogel) wrote :

Hmm, why was this "Won't Fix"?

A branch owner should be able to remove the subscription of anyone who would then not be able to resubscribe (as is the case with any current subscriber who is no longer on the team that allowed them to subscribe in the first place). There is no reason for subscription to be a one way street.

I've set status in both bug tasks to "Confirmed" for now; obviously it's up to the team to prioritize it, but I do think it's a valid bug; in fact I'll mention it on https://dev.launchpad.net/LEP/BetterPrivacy too. But I don't mean to start a status-reversion war -- if setting to "Confirmed" wasn't the right thing to do, let's discuss.

Changed in launchpad-code:
status: Won't Fix → New
Changed in launchpad:
status: Invalid → New
status: New → Confirmed
Changed in launchpad-code:
status: New → Confirmed
Curtis Hovey (sinzui)
affects: launchpad → null
Changed in null:
status: Confirmed → Invalid
Curtis Hovey (sinzui)
tags: added: disclosure
Changed in launchpad:
status: Confirmed → Triaged
importance: Undecided → Low
Curtis Hovey (sinzui)
Changed in launchpad:
importance: Low → High
Ian Booth (wallyworld)
Changed in launchpad:
assignee: nobody → Ian Booth (wallyworld)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
Ian Booth (wallyworld)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
no longer affects: null
Curtis Hovey (sinzui)
tags: added: privacy-transitions
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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