Thanks for the input Damir. I'm downloading your module today to try that out. As far as the last item on the Queview for Agents, I know that this is available in ticket search, but traditionally, engineers are lazy. I implemented a button on the search bar that allows the agent to click and see their tickets only. When you can make it easier for users, their more inclined to use it.
Bernie Frye Director, Technical Sales Engineering CURRENT Technologies, LLC 12800 Middlebrook Road, Suite 201 Germantown, Md. 20874 301-515-7617 ext. 214 240-793-9137 cell ***CONFIDENTIALITY NOTICE*** The information in this email may be confidential and/or privileged. This email is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this message from your system. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Damir Dzeko Sent: Tuesday, December 21, 2004 1:19 PM To: Development community of OTRS Subject: Re: [dev] What's on the development path? Hi Bernie, Frye, Bernie wrote: > > I'm about to run off and start developing some new modules which will > perform the following functions: > > > 1. Time to respond to the ticket > 2. Time the ticket was in the open state > 3. Time to close the ticket Have you seen my Report module? I've posted it here recently. > 4. Once the ticket is closed, stop the aging process on the ticket Age is simply time passed from creation of the ticket to the present moment. It cannot be stopped. :) But I must admit that it does not make much sense to see that some old ticket is 274 days of age. What you're really asking is to know how long ticket has been opened. Take a look at my Report module :) > 5. Send notifications to the agents when the ticket is in the new > state for 24 hours > 6. Send notifications to the agents when the ticket is in the open > state for 24 hours and no status has been sent to the customer > 7. Send notification to the agent when a ticket reaches XX days old > regardless of the number of status updates that have been sent to > the customer Perhaps GenericAgent could do that? (Haven't tried yet). > 8. Add a field linking ticket to our bug tracking system > 9. Add Stats reporting features for items 1,2 and 3 above. Please take look at my Report module. That's exactly what it's for. It calculates time the ticket spent in unanswered state (response time), the sum of time customer waited for an answer (total processing time), and total time ticket was opened. It reports that in two different values: real wall-clock minutes and business minutes (counting work-hours only). It provides CSV export so you can draw graphs and analyze it in some spread-sheet software. > 10. Enhance the current Stats reporting to display Pie Graphs, Bar > Graphs (in 3D) and be able to export them to Windows machines > properly (this seems to be a problem at the moment with version > 1.3.2) > 11. Add capability for an Agent to get a "QueueView" of their tickets > only Tried ticket search? Although, maybe it would be good to have some filtering mode in QueueView that would enable Agent to have more customized view on ticket queues. Regards, Damir _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
