One thing confuses me though: What the heck is the “Final Priority” field
good for?
Anyway, I’m hacking together full-text search for RT 1.0 (CVS) by wrapping
WWW::Search around htdig. Another search engine would do, but htdig is
free and I’m already running it. The idea is to get the serial_num by
parsing the filename, then use that to fetch the subject, area, owner,
requestor, and status from the database. It’s trivial to have WWW::Search
return a link URL built from serial_num. You can see the first bits of UI
at http://webserver.brandeis.edu/cgi-bin/rtsearch?search_for=kerberos
Rich Graves rcgraves@brandeis.edu
UNet Systems Administrator
Basically final priority is for the as-yet-unwritten
reprioritizer script that will raise or lower priority toward the final
priority as the due date approaches.
I installed RT last week and I really like it.
One thing confuses me though: What the heck is the “Final Priority” field
good for?
Anyway, I’m hacking together full-text search for RT 1.0 (CVS) by wrapping
WWW::Search around htdig. Another search engine would do, but htdig is
free and I’m already running it. The idea is to get the serial_num by
parsing the filename, then use that to fetch the subject, area, owner,
requestor, and status from the database. It’s trivial to have WWW::Search
return a link URL built from serial_num. You can see the first bits of UI
at http://webserver.brandeis.edu/cgi-bin/rtsearch?search_for=kerberos
Interesting. My one concern is that this allows searching of tickets a user
might not have access to.
jesse reed vincent – jrvincent@wesleyan.edu – jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
“Bother,” said Pooh, “Eeyore, ready two photon torpedoes and lock
phasers on the Heffalump, Piglet, meet me in transporter room three”
Basically final priority is for the as-yet-unwritten
reprioritizer script that will raise or lower priority toward the final
priority as the due date approaches.
Thanks,
Stephen Lawrence
-Support Technician & Webmaster
-Examen, Inc. -stephenl@examen.com
-916-921-4300 ext. 703
no. there is no way to do a search from within RT. This is fixed in 2.0.
The technical reason we store transaction content in textfiles dates back to the earliest days of RT … when it used mini-sql…which had no blob support.
RT 2 is designed against modern databases which allow such things
jesse> On the subject, is there currently a way to perform a keyword search through the comments of a closed ticket? Also, is there a technical reason why the transaction text is not saved in the db, but to text files? Jesse wrote:
Basically final priority is for the as-yet-unwritten
reprioritizer script that will raise or lower priority toward the final
priority as the due date approaches.
Thanks,
Stephen Lawrence
-Support Technician & Webmaster
-Examen, Inc. -stephenl@examen.com
-916-921-4300 ext. 703
jesse reed vincent – jrvincent@wesleyan.edu – jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
I admit that X is the second worst windowing system in the world, but all the
others I’ve used are tied for first.
Basically final priority is for the as-yet-unwritten
reprioritizer script that will raise or lower priority toward the final
priority as the due date approaches.
OK, I’ll either write the script or commment the whole thing out of the
web interface.
Basically you want something like
#!/bin/sh
mysql <<EOF;
use request_tracker;
1209600 seconds is two weeks
update each_req set priority = priority + 1
where priority < final_priority
and (
(
(UNIX_TIMESTAMP() - date_created > 1209600)
or (date_due - UNIX_TIMESTAMP() < 1209600)
)
);
EOF
which you could “just do” out of cron I suppose…
Anyway, I’m hacking together full-text search for RT 1.0 (CVS) by wrapping
WWW::Search around htdig. Another search engine would do, but htdig is
Interesting. My one concern is that this allows searching of tickets a user
might not have access to.
I’m working on that. It’ll use the same access control code as the queue
display. It looks like this will need to be hacked into the rtsearch
script, since it’s not taint/strict-clean enough to put in the base
WWW::Search::RTSearch module.
Rich Graves rcgraves@brandeis.edu
UNet Systems Administrator
no. there is no way to do a search from within RT. This is fixed in
2.0. The technical reason we store transaction content in textfiles
dates back to the earliest days of RT … when it used mini-sql…which
had no blob support. RT 2 is designed against modern databases which
allow such things
You still can’t index BLOBs in most databases, so if you have a lot of
tickets it will be slow and inefficient. I’ll probably stick with the
htdig wrapper hack for a while.
Oracle 8i Intermedia is getting there… I noticed a month or two ago that www.oracle.com had finally switched from an AltaVista search engine to
their own product. It won’t work reliably on Linux though.
Rich Graves rcgraves@brandeis.edu
UNet Systems Administrator
no. there is no way to do a search from within RT. This is fixed in
2.0. The technical reason we store transaction content in textfiles
dates back to the earliest days of RT … when it used mini-sql…which
had no blob support. RT 2 is designed against modern databases which
allow such things
You still can’t index BLOBs in most databases, so if you have a lot of
tickets it will be slow and inefficient. I’ll probably stick with the
htdig wrapper hack for a while.
nod The thought was to move “old” tickets to a data warehouse rt instance.
also, you’ll be able to cut down search time by limiting the search in other
ways…
Oracle 8i Intermedia is getting there… I noticed a month or two ago that www.oracle.com had finally switched from an AltaVista search engine to
their own product. It won’t work reliably on Linux though.
jesse reed vincent – jrvincent@wesleyan.edu – jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
Any e-mail sent to the SLA will immediately become the intellectual property
of the SLA and the author of said message will enter into a period of
indentured servitude which will last for a period of time no less than seven
years.
I would much rather have all the ticket information in one location personally.
Rich Graves wrote:
You still can’t index BLOBs in most databases, so if you have a lot of
tickets it will be slow and inefficient. I’ll probably stick with the
htdig wrapper hack for a while.
Oracle 8i Intermedia is getting there… I noticed a month or two ago that www.oracle.com had finally switched from an AltaVista search engine to
their own product. It won’t work reliably on Linux though.
Thanks,
Stephen Lawrence
-Support Technician & Webmaster
-Examen, Inc. -stephenl@examen.com
-916-921-4300 ext. 703
