Does anybody else think it would be useful if the Quick Search list
could be modified to include saved searches on a per user basis?
This way you could display summaries of categorized (by custom field)
tickets without displaying a list of tickets. This would make for a more
versatile rt dashboard. Of coarse you could set up a separate queue for
each category but this is overkill in some situations such as having one
queue for software issues with categories for bugs, feature requests etc.
I don’t know how difficult this is to implement however.
Does anybody else think it would be useful if the Quick Search list
could be modified to include saved searches on a per user basis?
I think that this might want to be another portlet, but I’d love to see
it happen.
There is something similar at RT3 Scripts - School of Computing - University of Kent
At the bottom, there is a set of callbacks, one of which puts a list
of saved searches in the left navigation column. (I know I found out
about this from the wiki, but I can’t find the reference on
the wiki right now.) FWIW, we really like these; the colorizing
and a couple extra menu options add a very nice polish to the experience.
(I didn’t write these, I just like them. Tim Bishop gets the credit.)
Does anybody else think it would be useful if the Quick Search list
could be modified to include saved searches on a per user basis?
I think that this might want to be another portlet, but I’d love to see
it happen.
There is something similar at RT3 Scripts - School of Computing - University of Kent
At the bottom, there is a set of callbacks, one of which puts a list
of saved searches in the left navigation column. (I know I found out
about this from the wiki, but I can’t find the reference on
the wiki right now.) FWIW, we really like these; the colorizing
and a couple extra menu options add a very nice polish to the experience.
(I didn’t write these, I just like them. Tim Bishop gets the credit.)
bobg
This way you could display summaries of categorized (by custom field)
tickets without displaying a list of tickets. This would make for a more
versatile rt dashboard. Of coarse you could set up a separate queue for
each category but this is overkill in some situations such as having one
queue for software issues with categories for bugs, feature requests etc.
I don’t know how difficult this is to implement however.
Does anybody else think it would be useful if the Quick Search list
could be modified to include saved searches on a per user basis?
I think that this might want to be another portlet, but I’d love to
see it happen.
There is something similar at RT3 Scripts - School of Computing - University of Kent
At the bottom, there is a set of callbacks, one of which puts a list
of saved searches in the left navigation column. (I know I found
out
about this from the wiki, but I can’t find the reference on
the wiki right now.) FWIW, we really like these; the colorizing
and a couple extra menu options add a very nice polish to the
experience.
(I didn’t write these, I just like them. Tim Bishop gets the
credit.)
bobg
This way you could display summaries of categorized (by custom
field) tickets without displaying a list of tickets. This would make
for a more versatile rt dashboard. Of coarse you could set up a
separate queue for each category but this is overkill in some
situations such as having one queue for software issues with
categories for bugs, feature requests etc.
I don’t know how difficult this is to implement however.
I also could not get this to work and spent a great deal of time trying
to get it to work, and none of the ways to give it a .rtrc file worked
for me. In the end, since I was running it from a perl script, I had no
choice but to run export RTSERVER=http://foo.bar;export RTUSER=foo; rt show foobar
John James wrote:
Hi
Just started running RT 3.6.1, web and email fine AFAIK, but I cannot get
the CLI to work.
I also could not get this to work and spent a great deal of time trying
to get it to work, and none of the ways to give it a .rtrc file worked
for me. In the end, since I was running it from a perl script, I had no
choice but to run export RTSERVER=http://foo.bar;export RTUSER=foo; rt show foobar
John James wrote:
Hi
Just started running RT 3.6.1, web and email fine AFAIK, but I cannot get
the CLI to work.
Regardless, this doesn’t deal with the issue that in rt-3.6.1 .rtrc
implementation doesn’t seem to work, and I’d love to know if anyone
knows why…
For reference, John, you don’t store the password in the .rtrc or pass
it as an environment variable, you manually run it once as whatever user
rt will run as and it will ask you for the password, once done it
creates a .rt_sessions file in that user’s home directory and doesn’t
ask for the password again for that user – or at least that’s how it’s
worked for me.
John James wrote:
Thanks to Mike’s comment I sorted it:
The mail gateway doesn’t use DNS. I had to use the actual (remote) ip in the
address
I also could not get this to work and spent a great deal of time trying
to get it to work, and none of the ways to give it a .rtrc file worked
for me. In the end, since I was running it from a perl script, I had no
choice but to run export RTSERVER=http://foo.bar;export RTUSER=foo; rt show foobar
John James wrote:
Hi
Just started running RT 3.6.1, web and email fine AFAIK, but I cannot get
the CLI to work.
Does anybody else think it would be useful if the Quick Search list
could be modified to include saved searches on a per user basis?
I think that this might want to be another portlet, but I’d love to see
it happen.
Attached is a basic solution to display summaries of Saved Searches in
the Quick Search list. Any Saved Searches added to your "RT at a glance
Summary" preferences will be added to the bottom of the list. A new
title bar separates them from the queue summaries.
This was achieved by placing a butchered version of “QueueSummary” in
local/html/Elements
A modified MyRT is also included to turn off the actual Saved Search
Ticket list in the Summary section of the homepage.
This was modified on RT-3.6.0 but seems to work on 3.6.3, however none
of the changes to MyRT or ShowSearch (from where a lot of code was cut)
in 3.6.3 have been implemented.
It needs a lot of tidying up, and a new portlet would probably still be
more desirable.