Registry: cannot convert private-membership to private
Bug #385978 reported by
Joey Stanford
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Brad Crittenden | ||
Bug Description
Hi,
Attempting to convert a private-membership team, with a private mailing list, to a "full" private team fails.
"This team cannot be made private since it is referenced by a mailing list."
I believe this constrain can be relaxed when going from private-membership to private and vice versa since the mailing list will already be private.
Thanks,
Joey
| tags: | added: oem-services |
| affects: | launchpad → launchpad-registry |
| tags: | added: privacy |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in launchpad-registry: | |
| assignee: | nobody → Brad Crittenden (bac) |
| importance: | Undecided → High |
| milestone: | none → 2.2.6 |
| status: | New → Triaged |
| tags: | added: story-private-teams |
| Changed in launchpad-registry: | |
| status: | Triaged → In Progress |
Revision history for this message
| Brad Crittenden (bac) wrote | #2 |
| Changed in launchpad-registry: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Curtis Hovey (sinzui) wrote Bug 385978 Fix released | #3 |
| Changed in launchpad-registry: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is intentional. Brad will prepare a migration plan from private membership to private. The principle issue is that no team should become private without first understanding that their name is already public, they will never be as private as a team that was created to be private.