History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: CHD-1873
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Assignee: Unassigned
Reporter: Niek Beernink - Oxilion
Votes: 1
Watchers: 1
Operations

Clone this issue
If you were logged in you would be able to see more operations.
Cerberus Helpdesk

Make the audit log searchable when it's enabled.

Created: 11/May/10 12:33 AM   Updated: 30/May/11 05:58 PM
Fix Version/s: 5.4

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

Value: 2 - Significant Value
Marquee: Mail, Usability


 Description   
After a week of using Cerberus (we switched from an exchange enviroment) one question seems to stick out:

How do I find that one mail I just closed without a reply?

Currently it seems impossible to search for mail closed by a specific worker without a reply. If I enable the auditlog and look at a closed e-mail I see that the closed property has been modified by a specific worker. Making it possible to search through all these properties when the auditlog plugin is enabled would enable us to find these e-mails as well.

The reason we close e-mail without a reply is because we also use Cerberus to process our orders. Our purchase system sends an e-mail to one of the addresses configured in Cerberus, we process it and close the e-mail when the order has been handled.


 All   Comments   Work Log   Change History      Sort Order:
I should also note that we're currently using Version 4.3.1 Stable (Build 951)

Comment by Damien R [05/May/11 02:51 AM]
Yes, depending on the way this is implemented it could be very useful for us too.

With a sea of tickets / checkboxes it's easy to sometimes perform an incorrect operation on a ticket (close the wrong one, or mark it as spam etc.) accidentally. Some way to search the audit log and/or view operations performed by each user by time would really help in these cases.

E.g. Worker X knows he closed a ticket accidentally during the last 24 hrs, but he doesn't know what the ticket was / about etc. so can't search for it. His action was recorded in the audit log so it should be possible "in theory" to search for all Worker X actions in the last 24 hrs to find the one in question; obviously with all of those timestamped it can be quite easy to find the particular tickets he worked on around the desired time (e.g. he thinks it was about 13:00) and take care of it.

But Niek, the cool kids are using v5 these days... Why did you only just start using Cerberus but yet you're in v4?

Comment by Damien R [05/May/11 02:52 AM]
Scratch that last question! ... **goes away to learn about the difference between 2010 and 2011**

This can be closed now since the audit log is no more and the activity log is searchable through filters.

Comment by Scott Luther [30/May/11 05:58 PM]
Resolved as of 5.4 with the new Activity Log