Bug #5277
closed
The problem the user is referring to is the remove connection button in "Manage Connections With Me". Using the remove connection CB Menu item doesn't cause this. The reason is the "Manage Connections With Me" seams to be using the wrong endpoint (the denyconnection endpoint), but maybe this behavior is intentional?
So to explain the scenario you'd have the below.
Mutual Consent: No
Cross Connections: No
1. User A connections to User B.
2. User B logs in.
3. User B navigates to manage connections.
4. User B selects "Manage Connections With Me" tab.
5. User B sees User A.
6. User B clicks the X to remove the connection FROM User A TO User B.
- Status changed from Assigned to Feedback
- Assignee deleted (
krileon)
with
Mutual Consent: No
Cross Connections: No
is user A connects with user B, then user B is not connected with user A.
I guess user B does not even need to be aware that user A has connected with him as he has no permission to alter this one way incoming connection.
At most - maybe future feature - user B can have a list of users that are connected to him (like a following me tweeter list).
- Target version changed from CB 2.0.9 to CB 2.0.10
This seems to work as designed from the explanations.
- Target version changed from CB 2.0.10 to CB 2.0.11
- Target version changed from CB 2.0.11 to CB 2.0.12
- Target version changed from CB 2.0.12 to CB 2.0.13
- Target version changed from CB 2.0.13 to CB 2.0.14
- Target version changed from CB 2.0.14 to CB 2.0.15
- Target version changed from CB 2.0.15 to CB 2.1
- Status changed from Feedback to Rejected
- Target version deleted (
CB 2.1)
- % Done changed from 0 to 100
This is working as intended. A user should be permitted to remove people who have directly connected to them. I believe the user reporting this needs something more along the lines of Following type functionality that CB Activity will provide.
Also available in: Atom
PDF