[rt-users] Auditing ticket accesses

[Flynn, Timothy J]

Jesse I think they just want to see for a particular ticket who accessed
it and when.  It would be nice if it was searchable and reportable so
another table does make sense.  But I am not sure how another table
would be accessed from RT.  I also liked the idea of a mutivalue custom
field.  For each user that accessed a ticket it could have 1 entry.

-Tim 



Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
-----Original Message-----
From: Jesse Vincent [mailto:jesse at bestpractical.com] 
Sent: Friday, April 24, 2009 7:18 PM
To: Flynn, Timothy J
Cc: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Auditing ticket accesses




On Fri 24.Apr'09 at 12:25:35 -0500, Flynn, Timothy J wrote:
> I am looking for a way to record when someone views a ticket and log 
> it somehow.  I know the url accesses are in apache logs.  I am looking

> for something long term that people could easily see when a ticket was

> accessed, by who, and when.  I was thinking about a scrip to do this 
> to record instances to a ticket itself.  Also the RT logfile came to 
> mind but it is full of other messages and errors.  Has anyone done 
> something similar?

I think an on-display callback that wrote to a custom table or custom
logfile would be your best bet. Do you care about accesses to subpages,
ticket search results, CLI usage, or API usage?