Cannot set team membership policy when creating a team in the person picker
Bug #1039692 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
When I create a team in the person picker, I do not see the default team membership policy (Restricted). When I try to set it, the ChoiceSource is empty. I can see on the +simplenewteam that provides the form that the membership policy is select that defaults to Restricted. I image that the either the view or the javascript does not know how to represent the enum.
Related branches
lp:~wallyworld/launchpad/add-project-membership-policy-1039692
- Curtis Hovey (community): Approve (code)
-
Diff: 47 lines (+14/-1)3 files modifiedlib/lp/registry/browser/pillar.py (+1/-0)
lib/lp/registry/browser/product.py (+1/-1)
lib/lp/registry/browser/tests/test_product.py (+12/-0)
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Ian Booth (wallyworld) |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #2 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This only happens when stepping through the pages to create a new project. When editing an existing project, everything is as expected. The cause is that the views used for a new project creation steps do not have the membership policy data added to the json request cache.