OK-
I was trying to figure out why the priority of my tickets was not going
up. So I poked arround and found the rt-crontool file. AH-HA! I need to
set up a cron job somewhere to do this. However, rt-crontool does not
appear to be documented anywhere. I eventualy found ./rtcrontool --help,
but that was not very enlightening. I am looking to have the priority of my
tickets move from their origina priority at creation, twards their final
priority at due date. I am guessing I will need to set up a dummy user (rt3
perhaps) who is a member of the group rt, and have the rt-crontool executed
at regular intervals, what I can’t figure out are what options I would use
for rt-crontool. Any ideas?
Change the --search-arg argument to match the queue you want to escalate
priorities for. I do one cronjob per queue – there may be a more efficient
way to do this.
-AaronOn Tue, 17 Feb 2004, Duncan Pickard wrote:
OK-
I was trying to figure out why the priority of my tickets was not going
up. So I poked arround and found the rt-crontool file. AH-HA! I need to
set up a cron job somewhere to do this. However, rt-crontool does not
appear to be documented anywhere. I eventualy found ./rtcrontool --help,
but that was not very enlightening. I am looking to have the priority of my
tickets move from their origina priority at creation, twards their final
priority at due date. I am guessing I will need to set up a dummy user (rt3
perhaps) who is a member of the group rt, and have the rt-crontool executed
at regular intervals, what I can’t figure out are what options I would use
for rt-crontool. Any ideas?
I am looking to have the priority of my
tickets move from their origina priority at creation, twards their final
priority at due date. I am guessing I will need to set up a dummy user
(rt3
perhaps) who is a member of the group rt, and have the rt-crontool
executed
at regular intervals, what I can’t figure out are what options I would
use
for rt-crontool. Any ideas?
We used the rt-escalate and rt-remind scripts avaialble on this page:
If the ticket is at or past the due date when the script is run, the
priority becomes the max. It’s not clear to me from your description
(due in 1 day. However, we often change the due date), whether or not
the tickets are already past their due date, but it seems likely. Note
that if the due date is past, and the script bumps the priority to 99,
merely changing the due date won’t lower the priority.
Change the --search-arg argument to match the queue you want to
escalate
priorities for. I do one cronjob per queue – there may be a
more efficient
way to do this.
-Aaron
OK-
I was trying to figure out why the priority of my tickets
was not going
up. So I poked arround and found the rt-crontool file. AH-HA!
I need to
set up a cron job somewhere to do this. However, rt-crontool does
not
appear to be documented anywhere. I eventualy found
./rtcrontool --help,
but that was not very enlightening. I am looking to have the
priority of my
tickets move from their origina priority at creation, twards their
final
priority at due date. I am guessing I will need to set up a
dummy user (rt3
perhaps) who is a member of the group rt, and have the
rt-crontool executed
at regular intervals, what I can’t figure out are what options
I would use
for rt-crontool. Any ideas?
