I’m wondering how I would go about adding a “stalled” tickets column to the
Quick Search display on the dashboard. I’ve done a Google, but a lot of the
information seems to pertain to older versions of RT. I’m on RT 4.2.2.
I’ve looked at ./share/html/Elements/Quicksearch expecting to find some
clues, but alas, nothing. Can anyone point me in the right direction or just
tell me how to it?
I’m wondering how I would go about adding a “stalled” tickets column to the
Quick Search display on the dashboard. I’ve done a Google, but a lot of the
information seems to pertain to older versions of RT. I’m on RT 4.2.2.
I’ve looked at ./share/html/Elements/Quicksearch expecting to find some
clues, but alas, nothing. Can anyone point me in the right direction or just
tell me how to it?
Cheers,
Tom
Why do you want to add it to the quick search display?
I simply created a new saved search that I called “MineStalled”, then I
added it to the “RT at a glance” right above the “Quick search” portlet
by clicking on “Edit” in the upper right corner of the “RT at a glance”
page and adding the saved search.
I’m wondering how I would go about adding a “stalled” tickets column to the
Quick Search display on the dashboard. I’ve done a Google, but a lot of the
information seems to pertain to older versions of RT. I’m on RT 4.2.2.
I’ve looked at ./share/html/Elements/Quicksearch expecting to find some
clues, but alas, nothing. Can anyone point me in the right direction or just
tell me how to it?
I’m wondering how I would go about adding a “stalled” tickets column to the
Quick Search display on the dashboard. I’ve done a Google, but a lot of the
information seems to pertain to older versions of RT. I’m on RT 4.2.2.
I’ve looked at ./share/html/Elements/Quicksearch expecting to find some
clues, but alas, nothing. Can anyone point me in the right direction or just
tell me how to it?
Cheers,
Tom
Why do you want to add it to the quick search display?
I simply created a new saved search that I called “MineStalled”, then I
added it to the “RT at a glance” right above the “Quick search” portlet
by clicking on “Edit” in the upper right corner of the “RT at a glance”
page and adding the saved search.
Hope this helps.
Bye
Cris
Wardrop, I guess I misunderstood your request.
However, I already have a “stalled” column in the Quick Search portlet.
What am I missing now?
I’m wondering how I would go about adding a “stalled” tickets column to the
Quick Search display on the dashboard. I’ve done a Google, but a lot of the
information seems to pertain to older versions of RT. I’m on RT 4.2.2.
I’ve looked at ./share/html/Elements/Quicksearch expecting to find some
clues, but alas, nothing. Can anyone point me in the right direction or just
tell me how to it?
here:
share/html/Elements/QueueSummaryByStatus
(@statuses)
AW, stalled is here in standard RT. Did you played with Lifecycles?
I’m wondering how I would go about adding a “stalled” tickets column to the
Quick Search display on the dashboard. I’ve done a Google, but a lot of the
information seems to pertain to older versions of RT. I’m on RT 4.2.2.
I’ve looked at ./share/html/Elements/Quicksearch expecting to find some
clues, but alas, nothing. Can anyone point me in the right direction or just
tell me how to it?
Quick Search displays all active and initial statuses as defined by
Lifecycles. Stalled is an active status by default in RT and so
stalled shows up by default. What modifications have you made?
Within “share/html/Elements/Quicksearch” there’s a toggle for switching
between QueueSummaryByLifecycle and QueueSummaryByStatus. I changed
$SplitByLifecycle to 0 and indeed, stalled now displays in Quick Search on
the dashboard, but I still want to see “Resolved” tickets. So I want 4
columns: new, open, stalled and resolved. I assume I need to change the
“QueueSummaryByStatus” view to show these 4 columns, but it’s not
immediately obvious how this view chooses which statuses to display.
I found a @statuses argument at the bottom of “QueueSummaryByStatus”. I
copied “QueueSummaryByStatus” into RT’s local directory and populated the @statuses variable/argument with ('new', 'open', 'stalled', 'resolved')
which works… but only every second page load. If I remove the logic that
checks whether the @statuses argument is set, it works on every page load.
Clearly there’s something weird with RT templates. I’ve noticed this
weirdness before.
Anyone have any clues as to what’s happening here?