Launchpad itself

Person.assigned_specs is an attractive nuisance

Bug #1068817 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Richard Harding

Bug Description

Person.assigned_specs returns every specification, regardless of its visibility. In its sole use, Person.deactivate_account, this is the correct behaviour. But the vast majority of the time, we want to know about specs visible to a given user, so Person.specifications(user, filter=[SpecificationFilter.ASSIGNEE]) should be used. This is obviously more cumbersome, tempting users to use the wrong thing most of the time.

Related branches

lp:~rharding/launchpad/remove_assigned_specs_1068817
Aaron Bentley (community): Approve
Diff: 101 lines (+15/-14)
4 files modified
lib/lp/registry/doc/person-account.txt (+5/-2)
lib/lp/registry/doc/person.txt (+3/-1)
lib/lp/registry/interfaces/person.py (+0/-2)
lib/lp/registry/model/person.py (+7/-9)
Curtis Hovey (sinzui)
tags: added: private-projects specifications
Richard Harding (rharding)
Changed in launchpad:
assignee: nobody → Richard Harding (rharding)
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :

Fixed in stable r16204 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/16204>.

tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Richard Harding (rharding)
tags: added: qa-ok
removed: qa-needstesting
Abel Deuring (adeuring)
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.
Subscribing...

Other bug subscribers

Remote bug watches

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