Hi,
I recently tested out the new RT::Extension::RepeatTicket module, it works out great, but the search feature is basically non-existence.
How could I search the original ticket which is GOING to repeat later on? Current situation there is no way to do this, please advise.
Hi,
I recently tested out the new RT::Extension::RepeatTicket module, it
works out great, but the search feature is basically non-existence.How could I search the original ticket which is GOING to repeat later
on? Current situation there is no way to do this, please advise.
Each ticket created in the recurrence should have a custom field called
Original Ticket with the id of the ticket that controls the recurrence.
Maybe you didn’t run the ‘make initdb’ step when installing to create
the custom field?
Dear Jim,
I did and it did show up. But the problem is that field only appear when ticket already repeat at least one time, am I correct? For example, now I create a recurrent ticket same month and day in next year, after 3 months and I did a search, OriginalTicket should not create as it haven’t been repeat, please clarify if something wrong in my concept. Thanks.
Thomas Lau
Senior Technology Analyst
Principle One Limited
27/F Kinwick Centre, 32 Hollywood Road, Central, Hong Kong
T +852 3555 2217 F +852 3555 2222 M +852 3555 2017
Hong Kong . Singapore . Tokyo-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Jim Brandt
Sent: Wednesday, May 15, 2013 7:46 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Flaws on RT::Extension::RepeatTicket search
On 5/14/13 10:26 PM, Thomas Lau wrote:
Hi,
I recently tested out the new RT::Extension::RepeatTicket module, it
works out great, but the search feature is basically non-existence.How could I search the original ticket which is GOING to repeat later
on? Current situation there is no way to do this, please advise.
Each ticket created in the recurrence should have a custom field called Original Ticket with the id of the ticket that controls the recurrence.
Maybe you didn’t run the ‘make initdb’ step when installing to create the custom field?
RT Training in Seattle, June 19-20: http://bestpractical.com/training
I did and it did show up. But the problem is that field only appear
when ticket already repeat at least one time, am I correct? For
example, now I create a recurrent ticket same month and day in next
year, after 3 months and I did a search, OriginalTicket should not
create as it haven’t been repeat, please clarify if something wrong
in my concept. Thanks.
You’re correct, the initial ticket doesn’t record a link to itself which
would allow you to search on it. To track down the repeating tickets
that haven’t repeated yet, look at the code in the rt-repeat-ticket
script you schedule in cron. It looks for all tickets with attribute
‘RepeatTicketSettings’. You could just put a debug statement in that
script to print the ticket id of each ticket, then run the script.
Then the following TicketSQL can be used:
HasAttribute = 'RepeatTicketSettings’On Fri, May 17, 2013 at 4:46 PM, Jim Brandt jbrandt@bestpractical.comwrote:
I did and it did show up. But the problem is that field only appear
when ticket already repeat at least one time, am I correct? For
example, now I create a recurrent ticket same month and day in next
year, after 3 months and I did a search, OriginalTicket should not
create as it haven’t been repeat, please clarify if something wrong
in my concept. Thanks.You’re correct, the initial ticket doesn’t record a link to itself which
would allow you to search on it. To track down the repeating tickets that
haven’t repeated yet, look at the code in the rt-repeat-ticket script you
schedule in cron. It looks for all tickets with attribute
‘RepeatTicketSettings’. You could just put a debug statement in that script
to print the ticket id of each ticket, then run the script.–
RT Training in Seattle, June 19-20: http://bestpractical.com/**traininghttp://bestpractical.com/training
Best regards, Ruslan.
Hi Jim,
How could you put a debug statement on the script?-----Original Message-----
From: Jim Brandt [mailto:jbrandt@bestpractical.com]
Sent: Friday, May 17, 2013 8:47 PM
To: Thomas Lau
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Flaws on RT::Extension::RepeatTicket search
I did and it did show up. But the problem is that field only appear
when ticket already repeat at least one time, am I correct? For
example, now I create a recurrent ticket same month and day in next
year, after 3 months and I did a search, OriginalTicket should not
create as it haven’t been repeat, please clarify if something wrong in
my concept. Thanks.
You’re correct, the initial ticket doesn’t record a link to itself which would allow you to search on it. To track down the repeating tickets that haven’t repeated yet, look at the code in the rt-repeat-ticket script you schedule in cron. It looks for all tickets with attribute ‘RepeatTicketSettings’. You could just put a debug statement in that script to print the ticket id of each ticket, then run the script.
Hi Jim,
How could you put a debug statement on the script?
In the run subroutine in rt-repeat-ticket:
while ( my $attr = $attrs->Next ) {
my $date = $args{date}->clone;
warn "Got a ticket with a recurrence: " . $attr->Object->id;
next unless $attr->Content->{'repeat-enabled'};
warn "Ticket with recurrence enabled: " . $attr->Object->id;
next if $args{ticket} && $args{ticket} != $attr->Object->id;
But it’s even easier to do as Ruslan suggested and create a new ticket
search, click Advanced, paste:
HasAttribute = ‘RepeatTicketSettings’
click Apply, then Show Results.