TrackRecord is a Ruby On Rails application which lets users enter and analyse timesheets, based around a framework of customers, projects and tasks. It may be useful for sole traders and small businesses.
BSD 3-Clause "New" or "Revised" License
12
stars
6
forks
source link
Optional (plugin?) postprocessing mechanism for reports #19
Although an organisation might adopt TrackRecord and find it suits their time recording and reporting needs reasonably well, they might at times do work for clients who require different styles of reporting. For example, a client may want worked hours each day rounded up/down to just a half-or-whole-day, with some client-specific strategy for dealing with under-accounted or over-accounted hours arising from the rounding.
Rather than try to build a whole bunch of such things directly into TrackRecord - though this would be possible - it is clearly preferable to have some kind of basic plugin mechanism to support different post-processors. The input would be a report's raw data, the output would be processed data in some other form. It ought to be possible, for example, to reimplement the CSV export feature in terms of such a plugin.
This enhancement is written with a particular requirement in mind from a real world deployment of TrackRecord so it's tempting to assign a milestone and rush it through, but given the potential scope of work, I'm reluctant to hold back v2.1 bugs or simpler enhancements for this particular feature. As a result it is at the time of writing not assigned to a milestone.
pond
commented
11 years ago
Although an organisation might adopt TrackRecord and find it suits their time recording and reporting needs reasonably well, they might at times do work for clients who require different styles of reporting. For example, a client may want worked hours each day rounded up/down to just a half-or-whole-day, with some client-specific strategy for dealing with under-accounted or over-accounted hours arising from the rounding.
Rather than try to build a whole bunch of such things directly into TrackRecord - though this would be possible - it is clearly preferable to have some kind of basic plugin mechanism to support different post-processors. The input would be a report's raw data, the output would be processed data in some other form. It ought to be possible, for example, to reimplement the CSV export feature in terms of such a plugin.
This enhancement is written with a particular requirement in mind from a real world deployment of TrackRecord so it's tempting to assign a milestone and rush it through, but given the potential scope of work, I'm reluctant to hold back v2.1 bugs or simpler enhancements for this particular feature. As a result it is at the time of writing not assigned to a milestone.