i can find no indication in the 1.05 code base that the “final priority” logic is implemented.
i’m not sure what the logic is even supposed to be – some vague sort of thing like “increase to this
value as due date approaches”.
this is just as well, since actually the reason i was checking was because i was thinking
about taking over the essentially useless field and replacing it with an “importance” or
"severity" field. i’d just use the same schema, but change the templates.
so i’d want to disable any special logic that might mess up my alternative use of that INT column.
it is generally useful to have distinct concepts of urgency and importance…
There is in fact no logic implemented for final priority.
it is generally useful to have distinct concepts of urgency and importance…
nod it’s something that will likely get folded in down the line.
thanks,
jOn Fri, Nov 24, 2000 at 10:35:18AM -0800, Mark D. Anderson wrote:
i can find no indication in the 1.05 code base that the “final priority” logic is implemented.
i’m not sure what the logic is even supposed to be – some vague sort of thing like “increase to this
value as due date approaches”.
this is just as well, since actually the reason i was checking was because i was thinking
about taking over the essentially useless field and replacing it with an “importance” or
“severity” field. i’d just use the same schema, but change the templates.
so i’d want to disable any special logic that might mess up my alternative use of that INT column.
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.