Suppressing priority messages

Hello all,
We have a RT escalation script which is run every hour to increase
the priority level of a ticket. In doing so, it creates a lot of noise
within the work order itself, placing "Enoch Root - Priority changed"
everytime its increased. I was wondering if its possible to suppress
those messages?

RT version: 4.0.1

Thanks,
Jason

Hello all,
We have a RT escalation script which is run every hour to
increase the priority level of a ticket. In doing so, it creates a
lot of noise within the work order itself, placing “Enoch Root -
Priority changed” everytime its increased. I was wondering if its
possible to suppress those messages?

Without knowing what the script does, that’s hard to say.
One of the RT::Actions available to rt-crontool has a “skip the
transaction” message, the other doesn’t. If you’ve written custom
code, you can steal the skipping code from the correct RT::Action

-kevin

Here is the code, I believe this was custom written by a previous employee:

#!/usr/bin/perl

use strict;

use warnings;

Points to the RT4 library

use lib ("/opt/rt4/lib","/opt/rt4/local/lib");

my $crontool = “/opt/rt4/bin/rt-crontool”;

package RT;

use RT::Interface::CLI qw(CleanEnv);

#Clean our the environment

CleanEnv();

Load the RT configuration

RT::LoadConfig();

Initialise RT

RT::Init();

my $queues = new RT::Queues($RT::SystemUser);

$queues->LimitToEnabled();

while (my $queue = $queues->Next) {

 my $queuename = $queue->Name;

 system("$crontool --search RT::Search::ActiveTicketsInQueue " .

        "--search-arg \"$queuename\" ".

        "--action RT::Action::EscalatePriority");

}

$RT::Handle->Disconnect();

exit 0;On 07/22/2011 09:04 AM, Kevin Falcone wrote:

On Fri, Jul 22, 2011 at 08:59:05AM -0400, Jason Brown wrote:

Hello all,
We have a RT escalation script which is run every hour to
increase the priority level of a ticket. In doing so, it creates a
lot of noise within the work order itself, placing “Enoch Root -
Priority changed” everytime its increased. I was wondering if its
possible to suppress those messages?
Without knowing what the script does, that’s hard to say.
One of the RT::Actions available to rt-crontool has a “skip the
transaction” message, the other doesn’t. If you’ve written custom
code, you can steal the skipping code from the correct RT::Action

-kevin


2011 Training: http://bestpractical.com/services/training.html

Here is the code, I believe this was custom written by a previous employee:

Read the docs for EscalatePriority vs LinearEscalate (you can perldoc
the .pm files in your RT tree).

LinearEscalate can be silent, but uses a different algorithm.

If you can’t change algorithms, you can port the features of
LinearEscalate to EscalatePriority and send in a patch

-kevin

Thanks Kevin, that fixed my issue.On 07/22/2011 09:53 AM, Kevin Falcone wrote:

On Fri, Jul 22, 2011 at 09:15:22AM -0400, Jason Brown wrote:

Here is the code, I believe this was custom written by a previous employee:

Read the docs for EscalatePriority vs LinearEscalate (you can perldoc
the .pm files in your RT tree).

LinearEscalate can be silent, but uses a different algorithm.

If you can’t change algorithms, you can port the features of
LinearEscalate to EscalatePriority and send in a patch

-kevin

#!/usr/bin/perl

use strict;

use warnings;

Points to the RT4 library

use lib ("/opt/rt4/lib","/opt/rt4/local/lib");

my $crontool = “/opt/rt4/bin/rt-crontool”;

package RT;

use RT::Interface::CLI qw(CleanEnv);

#Clean our the environment

CleanEnv();

Load the RT configuration

RT::LoadConfig();

Initialise RT

RT::Init();

my $queues = new RT::Queues($RT::SystemUser);

$queues->LimitToEnabled();

while (my $queue = $queues->Next) {

  my $queuename = $queue->Name;

  system("$crontool --search RT::Search::ActiveTicketsInQueue " .

         "--search-arg \"$queuename\" ".

         "--action RT::Action::EscalatePriority");

}

$RT::Handle->Disconnect();

exit 0;

On 07/22/2011 09:04 AM, Kevin Falcone wrote:

On Fri, Jul 22, 2011 at 08:59:05AM -0400, Jason Brown wrote:

Hello all,
We have a RT escalation script which is run every hour to
increase the priority level of a ticket. In doing so, it creates a
lot of noise within the work order itself, placing “Enoch Root -
Priority changed” everytime its increased. I was wondering if its
possible to suppress those messages?

Without knowing what the script does, that’s hard to say.
One of the RT::Actions available to rt-crontool has a “skip the
transaction” message, the other doesn’t. If you’ve written custom
code, you can steal the skipping code from the correct RT::Action

-kevin


2011 Training: [1]http://bestpractical.com/services/training.html

References

Visible links
1. http://bestpractical.com/services/training.html

2011 Training: http://bestpractical.com/services/training.html


2011 Training: http://bestpractical.com/services/training.html

Hello all,
We have a RT escalation script which is run every hour to
increase the priority level of a ticket. In doing so, it creates a
lot of noise within the work order itself, placing “Enoch Root -
Priority changed” everytime its increased. I was wondering if its
possible to suppress those messages?

RT version: 4.0.1

Thanks,
Jason

Hi Jason,

I would be very interested in how your workflow handles the priority
escalation every hour. We tried escalating the priority daily, but
since no additional resources were actually tied to the ticket
priority, the end result was to have most non-trivial tickets sitting
at the maximum priority.

The way we dealt with the priority change messages was to add a
"full headers" and a “brief headers” button on the ticket display.
The default was brief which did not display most of the internal
bookkeeping changes. This also improved the display speed.

Regards,
Ken

Ken,
We are using a tiered approach as part of our priority system. For
instance, highest priority tickets would have a range from 90-100,
medium priority tickets from 60 - 100, and lower tickets start at 1.
Along with their priority, they also have an associated time frame of
completion. A break and fix scenario would need to be completed
immediately if it affected the entire company whereas if it only
impacted one individual and there was a work around (such as a dead
keyboard) it would need to be resolved within three days. Other time
frames would be; improvements to a particular system would be completed
within 30 days and projects are TBD which is dependent upon their
scope. The team checks into RT periodically throughout the day and
takes work orders which focus on their job roles.

I have used this same type of work flow in the past when I worked for a
university. The only difference was that our help desk made the
determination and assigned it appropriately (most of the time :slight_smile: ).
Projects were never apart of the work order system as they were tied
into a secondary system like MS Project.On 07/22/2011 10:21 AM, ktm@rice.edu wrote:

On Fri, Jul 22, 2011 at 08:59:05AM -0400, Jason Brown wrote:

Hello all,
We have a RT escalation script which is run every hour to
increase the priority level of a ticket. In doing so, it creates a
lot of noise within the work order itself, placing “Enoch Root -
Priority changed” everytime its increased. I was wondering if its
possible to suppress those messages?

RT version: 4.0.1

Thanks,
Jason

Hi Jason,

I would be very interested in how your workflow handles the priority
escalation every hour. We tried escalating the priority daily, but
since no additional resources were actually tied to the ticket
priority, the end result was to have most non-trivial tickets sitting
at the maximum priority.

The way we dealt with the priority change messages was to add a
"full headers" and a “brief headers” button on the ticket display.
The default was brief which did not display most of the internal
bookkeeping changes. This also improved the display speed.

Regards,
Ken