[Tickets #6549] Support hours import from spreadsheet

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6549
-----------------------------------------------------------------------
 Ticket             | 6549
 Created By         | php at ideacode.com
 Summary            | Support hours import from spreadsheet
 Queue              | Hermes
 Type               | Enhancement
 State              | New
 Priority           | 1. Low
 Milestone          | 
 Patch              | 
 Owners             | 
-----------------------------------------------------------------------


php at ideacode.com (2008-03-31 16:18) wrote:

When working on multiple projects simultaneously, it's tedious and somewhat
impractical to track hours one entry at a time.  Instead, a more convenient
way is to keep the hours in a spreadsheet (Excel, Open Office, hand-edited
CSV, etc.), then bulk upload those hours all at once.  

For example, I might work on 10-30 issues (tracked in Whups) in a given
day, and in no particular order.  It's only at the end of the day that I
really know how many hours accumulated on all the issues.  So, a natural
use would be to accumulate in a spreadsheet then upload all at once.

Two other reasons exist for bulk uploading: (1) you work off-line
("disconnected") and only reconcile your changes when you're in range of a
network, and (2) you want to upload historically tracked hours to bootstrap
your hermes database.

Before I go off and implement this, is there a model already in some Horde
project that I can review?  I know Turba has one; is it a good one to
model?

Other thoughts: I figure the required columns would be date, description,
and hours: any other non-supplied columns would be defaulted per a
user-specified value.  Additionally, the order wouldn't be important, but
headers would be checked for the order.  I also figure the description
would match against any cost objects: if not exactly one cost object match,
that would be an error.  A summary should also be provided, so you can
cross check the values for upload accuracy.