Due Dates


#1

Due Dates dont seem to work when you create a Request

Glen Hollings
Global Info Links
Jnr Systems Administrator
ghollings@admin.gil.com.au


#2

Due Dates dont seem to work when you create a Request

Browse the list archive of this month, or grab the latest CVS
version of 1.0.6 for a solution to this problem.

Anyway, it seems that priority doesn’t raise when the date is due,
so there must be another bug like the last one.
I’ll take a look at this later.

Thomas

Email: tkoester@intevation.de
http://intevation.de/~tkoester/


#3

Due Dates dont seem to work when you create a Request

Browse the list archive of this month, or grab the latest CVS
version of 1.0.6 for a solution to this problem.

Anyway, it seems that priority doesn’t raise when the date is due,
so there must be another bug like the last one.
I’ll take a look at this later.

That’s actually a different issue. The priority escalation stuff was
for functionality that was never implemented. I seem to recall that someone
posted a shell script that could be run from cron to fix this, but I don’t
know where it got to. If somoene can point me at the message in the archives
or bounce me another copy, I’ll drop it in /contrib.

    -j

Thomas


Email: tkoester@intevation.de
http://intevation.de/~tkoester/


Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

that’s security the same way that asking for directions to topeka and
being told that a seal is a mammal is informative
-robin@apocalypse.org


#4

| That’s actually a different issue. The priority escalation stuff was
| for functionality that was never implemented. I seem to recall that
| someone posted a shell script that could be run from cron to fix this,
| but I don’t know where it got to. If somoene can point me at the message
| in the archives or bounce me another copy, I’ll drop it in /contrib.
±–>8

Message-ID: 39FCECD5.8000101@seindal.dkDate: Mon, 30 Oct 2000 04:36:53 +0100

Organization: Seindal Consult
To: Request Tracker Users rt-users@lists.fsck.com
Subject: [rt-users] Adjusting priorities

Dear RT-users,

This little script will adjust the priority of all open and non overdue tickets towards the final priority. The change is linear so each tickets priority moves from the initial priority towards the final priority at a constant speed. A tickets priority will only be changed upwards, so a ticket that has had its priority raised won’t have it lowered automatically. The opposite is not true, so a ticket that has been given a lower priority will have it raised again.

This script will have no effect on tickets that are not open or stalled, tickets without a due date, and tickets where the final priority is equal to the initial priority.

#!/bin/sh
mysql rt <<EOF
update each_req set priority=greatest(priority,
round((final_priority-initial_priority)/(date_due-date_created)
*(unix_timestamp()-date_created) +initial_priority))
where date_due > unix_timestamp()
and status in (‘open’,‘stalled’);
EOF

– René Seindal (rene@seindal.dk) http://www.seindal.dk/rene/

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

– brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university [“better check the oblivious first” -ke6sls]


#5

Date: Mon, 30 Oct 2000 04:36:53 +0100

This little script will adjust the priority of all open and non overdue tickets towards the final priority. The change is linear so each tickets priority moves from the initial priority towards the final priority at a constant speed. A tickets priority will only be changed upwards, so a ticket that has had its priority raised won’t have it lowered automatically. The opposite is not true, so a ticket that has been given a lower priority will have it raised again.

This script will have no effect on tickets that are not open or stalled, tickets without a due date, and tickets where the final priority is equal to the initial priority.

#!/bin/sh
mysql rt <<EOF
update each_req set priority=greatest(priority,
round((final_priority-initial_priority)/(date_due-date_created)
*(unix_timestamp()-date_created) +initial_priority))
where date_due > unix_timestamp()
and status in (‘open’,‘stalled’);
EOF

Good idea. I’ve modified this a little bit:

#!/bin/sh
mysql rt <<EOF
update each_req set priority=greatest(priority,least(final_priority,
round((final_priority-initial_priority)/(date_due-date_created)
*(unix_timestamp()-date_created)+initial_priority)))
where final_priority > priority
and date_due > date_created
and status in (‘open’,‘stalled’);
EOF
exit $?

Now the priority will be set to the final_priority even if the
script is run a few minutes after date_due.

Thomas

Email: tkoester@intevation.de
http://intevation.de/~tkoester/