Create Private and Private Security policies if sharing policy allows them

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

Bug Description

setBugSharingPolicy and setBranchSharingPolicy create Proprietary and Embargoed access policies when they're enabled, but not Private or Private Security. This is a problem if a project's initial policies are pruned because they're forbidden and unused, but the project is later reconfigured to allow non-Proprietary types.

The code to create the Private and Private Security policies as part of creating a new product should be removed, and set*SharingPolicy taught to create them instead. This will depend on Ian's branch to set the sharing policies on creation.

Related branches

William Grant (wgrant)
description: updated
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
assignee: nobody → Steve Kowalik (stevenk)
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
Steve Kowalik (stevenk)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
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.