This is only sort of a request. I had hoped to be able to use this module without having to install the Support Ticketing System. Turns out I was able to fork Support Timer, making it stand alone and adding some small improvements. Most of these improvements are general - such as changing the text on the start/stop button; allowing one to set a default starting time; and allow one to decide where in the content type it will appear. The idea is to focus on the core functionality - tracking time, and let people decide for themselves how to associate it - e.g. they can build their own Views from the time logs.

It's working name is Time Log and doesn't have a home on Drupal yet.

CommentFileSizeAuthor
time_log.tar_.gz10.36 KBnubeli

Comments

jeremy’s picture

jeremy commented
Status: Active » Needs work

I'd not be opposed to merging in changes that make integration with the support module optional. If you can provide this as a patch, I'll take a look...

nubeli’s picture

nubeli commented

I'm not sure what parts of what I posted you'd want to integrate. I was taking a different approach where the timer was closer to a generic CCK field. Then one could add cck date fields, cck select fields (for billing rates, etc), and so on. I removed the fields related to the timer (date, ticket info) so that someone can put whatever fields they want on the node.

So a lot of the functionality related to the support ticket system could be disabled or not installed. I'm not sure how much you can separate the functionality without messing up your system.

The functionality that may be useful for some which I had added to my version is:
- timer doesn't start automatically (maybe add as option in settings)
- Timer button changes to "Pause" when it's started, and "Start" when it's stopped (easily added)
- Allows admin to set a default starting time (we wanted each timer to have six minutes at start)
- Can add time logs to Views (with timer, date, etc as regular fields exposed to Views)

I didn't get as far as making the timer a CCK field but that's the direction I was hoping for so that we and others could build a site completely independent of Support Ticketing system.

Since I had changed some of the basics of the timer I'm not sure if submitting a patch would get accepted.

jeremy’s picture

jeremy commented

> - timer doesn't start automatically (maybe add as option in settings)
A patch for this feature ideally would be submitted to this other issue:
#797390: Prevent Autostart?

> - Timer button changes to "Pause" when it's started, and "Start" when it's stopped (easily added)
That would be great, ideally create a new issue for this.

> - Allows admin to set a default starting time (we wanted each timer to have six minutes at start)
Interesting. If there's a clean admin-interface for this, sure. It should have hooks or alters allowing another module to further control this (ie I could see the support module enhancing this to be a per-client setting).

> - Can add time logs to Views (with timer, date, etc as regular fields exposed to Views)
Yes, if done cleanly I'd likely merge this.

Turning it into a generic CCK field would be a great direction; but it's important to me that we don't lose functionality in the process. We use the support_timer module for all our client invoicing, so the backend reporting is also important to us. Perhaps something comparable could be built through Views, but I'd not be committing a patch that breaks this without a functional replacement.