I think I got it.
RT::Tickets exposes DeleteRestriction, which
Takes the row Id of a restriction (From DescribeRestrictions' output, for
example.
Removes that restriction from the session's limits
Alberto Scotto
[Blue]
Via Cardinal Massaia, 83
10147 - Torino - ITALY
phone: +39 011 29100
al.sco...@reply.it
www.reply.it
From: Scotto Alberto
Sent: sabato 21 luglio 2012 20:12
To: rt-users@lists.bestpractical.com
Subject: How to efficiently filter tickets with LimitXXX methods of RT::Tickets?
Hi all,
I'm customizing the script
http://requesttracker.wikia.com/wiki/RtUnifiedreminder to send a daily report
about SLA, with the overdue tickets.
I have a series of nested loops, the main is for each QueueAdminCC send the
report to him/her.
In order to find the overdue tickets that are up to him/her, I'm using
RT::Tickets methods: LimitStatus, LimitDue, LimitQueue.
Here is the question.
Is there a way to cache some parts of filtering so that I don't have to start
filtering from the ground but use the results previously computed?
If APIs don't give anything specific, I think the only way is cloning the
object RT::Tickets after applying the general filters?
In the latter case, would you please give me some hints? Sorry for the dumb
question, I'm quite n00b with Perl.
Thank you all!
Alberto Scotto
[Blue]
Via Cardinal Massaia, 83
10147 - Torino - ITALY
phone: +39 011 29100
al.sco...@reply.it
www.reply.it
--
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.
inline: image001.pnginline: blue.png
