Unhelpful error message adding team A as a member of team B when team B is already member of team A

Bug #95193 reported by Diogo Matsubara
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Brad Crittenden

Bug Description

Steps to reproduce (using sample data):
1) Open http://launchpad.dev/~name18/+addmember
2) Add 'guadamen' as a member of 'name18'
3) Open http://launchpad.dev/~guadamen/+addmember
4) Try to add 'name18' to 'guadamen'
5) Get an unhelpful 'Constraints not satisfied' error message

Expected results:
A helpful message saying that the you can't add guadamen to name18 because name18 is already a member of guadamen.

Tags: lp-registry ui
Changed in launchpad:
importance: Undecided → Low
status: Unconfirmed → Confirmed
Revision history for this message
Jonathan Lange (jml) wrote :

This error is also raised when you try to add Team A as a member of Team A

Curtis Hovey (sinzui)
affects: launchpad-foundations → launchpad-registry
Revision history for this message
Karl Fogel (kfogel) wrote :

See also bug #297833, in which attempting to invite a private team to which you don't have access gives a "Constraint not satisfied" error. Similar symptom, but (apparently) different cause.

Curtis Hovey (sinzui)
Changed in launchpad-registry:
assignee: nobody → Brad Crittenden (bac)
status: Triaged → 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.