Project.* module integration and estimated versus actual time comparison
Benjamin Melançon - December 30, 2007 - 17:57
| Project: | Node time tracker |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Benjamin Melançon |
| Status: | active |
Jump to:
Description
I plan to follow the code for casetracker integration to provide the same functionality for Project module– providing the total hours on a project. Should we be looking at helper modules and a mini-API?
Or should this totaling be left to views?
I'd then like to have the option to automatically create a CCK field for estimated time for all nodes with node_time_tracker enabled, so that node_time_tracker is aware of it and reports of the difference can be made.
Thoughts?
benjamin, Agaric Design Collective

#1
sorry for such a late answer. yep, this sounds interesting. have you worked on this during this time? I'm working again on this module and it may be the right time to work on a fixed direction.
#2
About to just install your module again and use it right away in production and see how things go, and then what I can do with it.
Does it record the start and stop times anywhere, or just the total time?
Thoughts about Views integration?
benjamin, Agaric Design Collective