Somewhat urgent help required

RT Users
1

As a matter of some urgency, I REALLY need to configure RT to be able to
display the priority
in the main or “Home” window.

That is to say, the Home window should ideally appear somewhat like
this:

25 Highest Priority Tickets I Own…

         #Subject                                        Queue

Status Priority
2948 rt not displaying priority jobs
open 4 [Update]

Any advice on how to do this would be GREATLY appreciated.

I was hoping it could be done by adding something into the weboptions
hash in the config.pm file.
Something like this:

{ Header => ‘PriorityDisplay’,
TicketAttribute => ‘PriorityAsInt’
#or perhaps PriorityAsString…the Tickets table describes it as an
int(11)
}

This is, as a some of you would know, very similar to the way one would
add the DateDue
to the default display. (or so I have seen from the FAQ at any rate)

I would just like someone to tell me if
a) this is the correct way to do it
b) if the change I suggested will bring about the result I am looking
for
c) the syntax is correct?
d) i should be doing it some other way??

Thanks in advance

Dane

Dane Rapaport
Systems Administrator and All Round Nice Guy
Animal LOGIC, Fox Studios Australia
www.animallogic.com
p: +61 2 9383 4964
m: 0414 735 922

2

Dane Rapaport dane@al.com.au writes:

As a matter of some urgency, I REALLY need to configure RT to be
able to display the priority in the main or “Home” window.

25 Highest Priority Tickets I Own…

         #Subject                                        Queue

Status Priority
2948 rt not displaying priority jobs
open 4 [Update]

I was hoping it could be done by adding something into the
weboptions hash in the config.pm file. Something like this:

{ Header => ‘PriorityDisplay’,
TicketAttribute => ‘PriorityAsInt’
#or perhaps PriorityAsString…the Tickets table describes it as an
int(11)
}

I found this answered by searching the archives, but I just installed
RT for the first time a couple days ago, so it may not be optimal. In
fact it sounds like this doesn’t answer your question. This displays
Priority in the list of tickets once you’ve selected a queue, not on
your “home” page where you see all your tickets regardless of queue.
Hmmm, maybe it will help anyway?

%WebOptions=
(
ExtraTransactionActions => sub { return “”; },

 QueueListingCols =>
  [
   { Header     => 'Id',
     TicketLink => 1,
     TicketAttribute => 'Id'
     },

  { Header     => 'Subject',
     TicketAttribute => 'Subject'
     },
   { Header => 'Requestor(s)',
     TicketAttribute => 'RequestorsAsString'
     },
   { Header => 'Status',
     TicketAttribute => 'Status'
     },


   { Header => 'Queue',
     TicketAttribute => 'QueueObj->Name'
     },

   { Header => 'Priority',
     TicketAttribute => 'Priority'
     },

   [... the rest of the columns omitted ...]
3

Thanks to all who provided assistance with this.
It was truly appreciated.

Chris: I wasnt looking very closely at the commenting about the
weboption prototyping.
Yesterday, before any replies came through I already figured out the
{ Header => ‘Priority’,
TicketAttribute => ‘Priority’
},

and added it into the config.pm file and it worked.
Priority is now displayed on the tickets listed in the Search results.

With the advice from Jesse and rt_user, I can now modify the Home page
to
display the Priority as required.

Thanks again to Jesse et al.

Dane

Dane Rapaport
Systems Administrator and All Round Nice Guy
Animal LOGIC, Fox Studios Australia
www.animallogic.com
p: +61 2 9383 4964
m: 0414 735 922

4

Chris Shenton Chris.Shenton@hq.nasa.gov writes:

   { Header => 'Priority',
     TicketAttribute => 'Priority'
     },

I’ve got exactly that line in my config.pm, but it doesn’t work. It
just shows “-” in the listing. FinalPriority works. Any ideas on how
to get it to work?
/Ian D
ian@assv.net