Robert Blackwell

I use Request Tracker (RT) all the time for work and home projects. What this means is I am left with ticket litter--lots of directories with names like test, examples, ETL, Proof of Concepts, foo, bar, baz, x. It all adds up to lots of ticket litter. Now I have a ticket for everything I do. (More on that later.)

That left me with a new problem. I had directories full of ticket numbers. It became overwhelming, and I needed a solution.

And so was born Path::Iterator::Rule::RT.

Using two packages from CPAN this was easy work.
Path::Iterator::Rule
RT::Client::REST

Path::Iterator::Rule is extendable with custom rule subroutines. Using this with RT::Client::REST made it very easy to add RT ticket information into a rule to select directories.

Here are some examples using Path::Iterator::Rule::RT.

# This will print all tickets in the directory that have resolved tickets.

use Path::Iterator::Rule;
use Path::Iterator::Rule::RT;
my $rule = Path::Iterator::Rule->new;
$rule->status("resolved");
for my $file ( $rule->all(@ARGV) ) {
say $file;
}

This will print all tickets in the directory that have tickets in the General queue that were created yesterday. This is slightly tricky. The TicketSQL is not as it appears. It has id=directory name added to it.

So this
$rule->TicketSQL("Queue='General' AND Created = 'yesterday'");
becomes
"id=directory name AND Queue='General' AND Created = 'yesterday'"

use Path::Iterator::Rule;
use Path::Iterator::Rule::RT;
my $rule = Path::Iterator::Rule->new;
$rule->TicketSQL("Queue='General' AND Created = 'yesterday'");
for my $file ( $rule->all(@ARGV) ) {
say $file;
}