[rt-users] R: Use Query builder to find tickets which were closed after the became over due
Hi I'm afraid you can't. I've had the same problem, and I solved with some creativity, involving escalation. I decided that FinalPriority = 89 and, once LinearEscalate has brought one's ticket Priority to 89, then a rt-crontool job increments Priority by some value. So, in my searches, I can distinguish overdue/not overdue tickets by Priority, in this way: Priority > 89 => overdue Priority <= 89 => not overdue Hope this helps. Anyway I'd like to hear other (better) solutions to this problem. Regards Alberto Scotto [Blue] Via Cardinal Massaia, 83 10147 - Torino - ITALY phone: +39 011 29100 al.sco...@reply.it www.reply.it Da: rt-users-boun...@lists.bestpractical.com [rt-users-boun...@lists.bestpractical.com] per conto di Shrivallabh Deshmukh [shrivallabh.deshm...@sungard.com] Inviato: venerdì 17 agosto 2012 12.52 A: rt-users@lists.bestpractical.com Oggetto: [rt-users] Use Query builder to find tickets which were closed after the became over due HI. Can I compare 2 fields using query builder? For example, can I do a query which says display all fields which are closed after their due date? Regards, Shrivallabh -- The information transmitted is intended for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. <>
[rt-users] AutoRejectRequest Template not working?
All, I have RT 4.0.5 set up to accept mail and not create new users. I am using RT::Authen::ExternalAuth. I have a problem where some of my users are not using their original email address to send emails to RT. When they send an email into an RT monitored address they get three emails, “Could not load a valid user”, “User could not be loaded”, and “User could not be created”. I have added Set($LookupSenderInExternalDatabase, 1); Set($SenderMustExistInExternalDatabase, 1); But I do not think those are relevant to ExternalAuth. I have added the AutoRejectRequest Template globally, hoping that it would give my users a more graceful error message. Is there anyone to change the outgoing error messages so that a user doesn’t get three, and that the, hopefully, one message they get has more info in it? Anything I have found on this seems to be old, deprecated, or not using ExternalAuth. Thanks! April
Re: [rt-users] Using Ajax with Mason in RT
On 08/17/2012 04:30 AM, Paul Tomblin wrote: > If there is one thing that's annoyed me about my whole experience with > RT it's the way errors either get eaten up or mis-reported. I don't > know if that's the fault of Perl, Mason or RT, but I frequently find > myself having to put RT::Logger->debug statements every other line just > so I can figure out where it's silently failing, and then minutely > examining the line to discover that (as happened yesterday) I had an > extra $ in front of a variable name. Rarely in my experience do things completely silently fail. If you run across such reproducible cases where an error completely disappears, file a bug report. Mason often gets line numbers right, but sometimes doesn't because of the way it's implemented. If you're not in a Mason special block (<%args>, <%flags>), most pure Perl errors (from % lines or <%perl> or <%init>) are fairly explanatory. The special blocks are, well, special and Not Quite Perl.
[rt-users] REST API and Saved Searches
Greetings I am trying to use REAST API from excel and can do simple queries but want to use a saved search does anyone know of REST command line that can do this, I want to import the saved search out into a spreadsheet TIA Simon
Re: [rt-users] Using Ajax with Mason in RT
On Fri, Aug 17, 2012 at 3:26 AM, Martin Drasar wrote: > > Still, I wonder how come that Paul could successfully run my scripts... > > Because I didn't put it in Elements, I put it in the directory with the code I was working on, and because I didn't try it with <%flags>. If there is one thing that's annoyed me about my whole experience with RT it's the way errors either get eaten up or mis-reported. I don't know if that's the fault of Perl, Mason or RT, but I frequently find myself having to put RT::Logger->debug statements every other line just so I can figure out where it's silently failing, and then minutely examining the line to discover that (as happened yesterday) I had an extra $ in front of a variable name. -- http://www.linkedin.com/in/paultomblin http://careers.stackoverflow.com/ptomblin
[rt-users] Use Query builder to find tickets which were closed after the became over due
HI. Can I compare 2 fields using query builder? For example, can I do a query which says display all fields which are closed after their due date? Regards, Shrivallabh
[rt-users] Accessing Ticket from MakeClicky callback
Hi, is it possible to access ticket object from MakeClicky callback? For example, I have a callback that recognizes an IP and allows to perform set of actions on click. And for one of that action, I need to have current ticket subject. How can I get access to such information? Thanks, Martin
[rt-users] RT 4 Book advice please
I am looking for information on configuring RT 4.0.6, as it seems to be quite a lot different than 3.8. I have the RT Essentials [2005] bokk but perhaps there is something out now that is targeting RT4? thanks oliver -- Oliver Nash
Re: [rt-users] Using Ajax with Mason in RT
On 16.8.2012 18:48, Thomas Sibley wrote: > 403 is Forbidden. RT denies direct requests to /Elements/ directories > (among other internal components). This denial happens in RT's normal > request handling phase, which doesn't get called when you set inherit => > undef. Hi Thomas, thank you, moving it outside of elements to custom directory did the trick. It finally works! > Please just remove the <%flags> section all together. You also lose > things like encoding handling, not to mention authentication, when you > disable RT's request handling. I have gladly thrown it away... >> If I keep it, I get back following error: "syntax error at >> /home/RT/RT-4.0.6/local/html/Ticket/Elements/TestComponent line 15, at EOF" > > I'm betting it's the semicolon in the <%flags> section. Remove it. The > line number being off is Mason getting it wrong (I'll bet it's the line > # of the Mason object file). Heh, I am used to missing semicolon, not the other way round. Anyway this was really the cause. Removing it made it worked, although it is no longer necessary because of what was written before. Still, I wonder how come that Paul could successfully run my scripts... Anyway, big thanks to you. Martin