Forum OpenACS Development: Response to Software Development (Bugs, QA, etc) and OACS

My biggest feature request for any sort of ticket tracker/intranet
sort of thing is something not really suited to the web, but I think
it could be done:  a time tracker.  You know, an electronic
stopwatch.

My problem is this:  if I don't use one of these time tracking thing-
a-ma-bobs I don't ever get my time recorded (and even with one,
remembering to use it is a bit hit or miss).  So I have my file for
each project and my times tracked (on good days) for each task.
Cool.  But now if I want to have that time recorded in the ticket I
have to go look it up and enter it, possibly adding up multiple
times if it got split over several sessions.  Most of the time this
just ain't gonna get done.

A much better (for me) solution would be to have buttons right on
the "one ticket" page to start, stop and pause the clock.  Or even
a page where multiple tickets could be being tracked at once.
doing this should be really easy with a database behind the
scenes;  just save the stop and start times and compute the
difference.  Then, of course, granularity needs to be
configurable.

To make this really useful I'd also want a special kind of ticket
which wasn't a bug or a feature request, but more like a task list.
Then I could create one of these "todo" tickets for each of my
development tasks, just as I currently create line items in my
ticket tracker, and have everythigng tracked this way.  And I'd
want the ability to do time reports by project, of course. :)

My $0.02,