Re: dates, and priority as importance * urgency

In message <[email protected]>,
Tom Jones writes:
>We're currently using the default config as shipped with Debian 7.0.
>
>First is dates, with notifications.  Example: if a supplier says something
>will be delivered on a particular date, one wants to "wait" until that
>date, and then chase them.  In general it should be possible to put a
>ticket into a "waiting until this date" state.  Another example: a hard
>deadline: if we don't file our license renewal by this date, we lose a 
>license.
>
>I don't know whether roundup should know the "types" of deadline, such
>as "waiting on", "deadline", etc.  Or whether the user should be able
>to set up their own, with notification parameters.  I don't want to go
>too deep into the design at this point; rather, I just want to provide
>basic illustration of the feature.

If you look at http://www.cs.umb.edu/~rouilj/roundup/, that has an old
tracker (not compatible with 1.4.x), that has a schema and supporting
scripts that allows you to add an automatic action:

 automatic actions:

    actiondate - date on which action will occur
    actionstatus - the [optional] new status for the issue after the
          action triggers.
    actioncomment - the [optional] comment message that will be
          added to the issue when the action triggers.

there is a script that runs from cron that does the actual
notification.  This only supports one pending action. It could be
extended to support multiple actions or more likley you would want to
define an action class and have them link to one (or more) issues.

The script you run from cron would recognize the "types" of deadlines
and do whatever action is appropriate.

>Another feature is making priority a composite attribute.  At the moment
>it has 5 possible values (in the default config) from wish thru bug to 
>critical.  Many of us find it useful to think of priority as the product
>of importance * urgency.  I won't try to lay this out in full here, as
>googling for "importance urgency" gives pretty good results.

You may want to look at how I defined "Issue Priority" in the tracker
docs:

  http://www.cs.umb.edu/~rouilj/roundup/sysadmin_tracker_help.html

and see if that fills your needs. I always thought the "priority" in
the default tracker described categories more than priorities.
 
>There is possible integration between the two features.  As a hard 
>deadline approaches, it would become more urgent, thus increasing the
>overall priority.  Importance would not change as a function of time (tho
>of course a user may re-evaluated the importance when reviewing it).

Escallation can be done using a script run from cron.

Feel free to download the tracker tarball and see how the schema and
asscociated scripts are written. The tracker will NOT run on any
modern release of roundup because of changes to roundup over the
years. I have been doing some work on updating it for roundup 1.4.x
but the work isn't done yet.

If you think some code from the updated tracker may be useful, drop me
a line and I'll send you what I have.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.

------------------------------------------------------------------------------
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk