Switching users for the same party not being tracked

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a transaction in which a party is queued up via a To Do group.
2. User A who is in that group accesses the transaction.
3. Later, User B who also is in the group accesses the transaction.

What is the expected output? What do you see instead?
It appears that the system is only remembering that first user. The log records 
show the new user's actions, but the transaction details only shows the first 
user's information, not the second who actually completed it.

Original issue reported on code.google.com by yoz...@gmail.com on 22 Aug 2013 at 11:49

[GoogleCodeExporter]

It is possible this is a To Do bug when unlocking a transaction, it may not be 
transferring the party to track the fact that one accessed it and then another 
user accessed it.  The activity logs appear correct, but the party tracking 
should note that a new user has come into play.

Original comment by yoz...@gmail.com on 22 Aug 2013 at 11:54

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

What we found was that when you unlocked in To Do, it was just resetting a 
value rather than doing a "party transfer", which it should since it's changing 
from one person to another.  So, this will now track all users who access it 
from To Do separately (obviously only one user at a time can play the the party 
role), and if they unlock it so another can access it, it will also cause the 
"party retrieved document" event to fire again when the new party accesses it 
for the first time since it no longer considers the new person to be the same 
party.

Original comment by yoz...@gmail.com on 23 Aug 2013 at 11:40

• Changed state: Started
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Added to 13.8.10 patch 0824 release.

Original comment by yoz...@gmail.com on 25 Aug 2013 at 5:58

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****