Person.addMember (in the API) should make it clear that if a membership already exists it'll change its status and expiration date
Bug #284264 reported by
William Grant
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Person.addMember's documentation suggests that it should be used for altering membership status, and this appears to be the only way to do that. However, it recalculates the expiry date. This is wrong.
| Changed in launchpad: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in launchpad-registry: | |
| assignee: | nobody → salgado |
| milestone: | none → 2.1.11 |
| Changed in launchpad-registry: | |
| milestone: | 2.1.11 → 2.1.12 |
| Changed in launchpad-registry: | |
| milestone: | 2.1.12 → none |
| Changed in launchpad-registry: | |
| assignee: | salgado → nobody |
| importance: | Medium → Low |
| tags: | added: api |
To post a comment you must log in.
