{
  'Business Unit': ['Platform'],
  'Date of First Response': '2014-06-01T18:56:05.978-0500',
  "Is there anything you'd like to add?": "This is worse when rapidly paying multiple owners' objects, as at a Gatcha Faire event, such as the tremendously popular Arcade. The wrong transaction description will be used, making one seller believe they are getting another seller's payments. To reproduce this case, replicate the above object on a second account and rapidly alternate between paying the two objects.",
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': '* When rapidly paying objects, the same transaction description will be used several times. For example two or three source/destination payment pairs will use Destination: (myself) Payment Region: (my region) Description: <90.75000, 116.00000, 30.25000>:9 followed by several transactions with :12. 10 and 11 were skipped. However local chat shows that the object had been correctly renamed before each payment before I clicked to issue the new payment.',
  'What were you doing when it happened?': 'Create an object and add this script:\r\n{code}\r\ninteger count = 0;\r\n\r\nSetName()\r\n{\r\n    string name = (string)llGetPos() + ":" + (string)count;\r\n    llSetObjectName( name );\r\n}\r\n\r\ndefault\r\n{\r\n    state_entry()\r\n    {\r\n        llSetPayPrice( 1, [1,PAY_HIDE,PAY_HIDE,PAY_HIDE] );\r\n        SetName();\r\n    }\r\n\r\n    money( key id, integer amount )\r\n    {\r\n        llSay( 0, (string)id + " " + (string)amount );\r\n        count++;\r\n        SetName();\r\n    }\r\n\r\n}\r\n{code}\r\n\r\n* Make the object\'s default action click-to-pay\r\n* Rapidly click and pay the object several times\r\n* Note that after each payment, the object is renamed with its current coordinates, followed by a serial number that increments after each payment. Example: <90.75000, 116.00000, 30.25000>:9\r\n* View the transaction log at: https://accounts.secondlife.com/transaction_history\r\n',
  'What were you expecting to happen instead?': '* Expected the transaction descriptions to match the issued transaction',
}