Admin: 1 revision imported

2016-04-06T20:52:52Z

1 revision imported

← Older revision		Revision as of 16:52, 6 April 2016
(No difference)

BillCole: Created page with "It seems to me that while $Transaction->CreatorObj will be the right user when a ticket is created via email, this would be better (and maybe safer) if the code checked to ass..."

2014-04-23T22:25:28Z

Created page with "It seems to me that while $Transaction->CreatorObj will be the right user when a ticket is created via email, this would be better (and maybe safer) if the code checked to ass..."

New page

It seems to me that while $Transaction->CreatorObj will be the right user when a ticket is created via email, this would be better (and maybe safer) if the code checked to assure that there is only one member in $Ticket->Requestors and conditionally set the password for ''that'' user if they don't already have one. Referencing the Requestor instead of the Creator eliminates the edge cases that are hinted at by the current code checking for Nobody and Privileged status.

I believe that rework would make the password generation happen when a Privileged (i.e. support staff) user creates a ticket (i.e. in the web interface) with a single Requestor whose account lacks a password.

Talk:AutogeneratedPassword/@comment-BillCole-20140423222528 - Revision history

Admin: 1 revision imported

BillCole: Created page with "It seems to me that while $Transaction->CreatorObj will be the right user when a ticket is created via email, this would be better (and maybe safer) if the code checked to ass..."