OOPS adding private team to another private team
Bug #519306 reported by
Diogo Matsubara
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
j.c.sackett |
Bug Description
As seen on OOPS-1500EA522 a PrivatePersonLi
Related branches
lp:~jcsackett/launchpad/private-team-to-private-team-519306
- Brad Crittenden (community): Approve (code)
-
Diff: 152 lines (+64/-9)4 files modifiedlib/lp/registry/browser/tests/test_person_webservice.py (+1/-0)
lib/lp/registry/interfaces/person.py (+9/-4)
lib/lp/registry/tests/test_project.py (+3/-5)
lib/lp/registry/tests/test_team_webservice.py (+51/-0)
Changed in launchpad-registry: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in launchpad-registry: | |
assignee: | nobody → j.c.sackett (jcsackett) |
status: | Triaged → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad-registry: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is correct, and the UI does not let the user do it. The vocabularies prevent this from happening because it leaks information between the teams. The user of the API script is not using a value from the vocabulary. This is like using a distroseries when a product series is expect.