| skyronic | |
| Oct 18 2013, 8:19 AM |
| F72406: Screenshot_from_2013-10-18_13:55:50.png | |
| Oct 18 2013, 8:27 AM |
Reports showing:
All of this should allow controlling time.
A table showing time logged last week v/s previous weeks.
| Name | This week | Last Week |
|---|---|---|
| PersonA | 5 | 7 |
| PersonA | 5 | 7 |
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T4853 A "tracked time per project" would be really usefull for project manager. | ||
| Open | None | T3569 Make Phrequent somewhat usable | ||
| Open | None | T3985 Reporting for phrequent |
I've added a revision D7346: Very CRUDE implementation of reporting for phrequent which results in something like this:
Ideally we might want to plug this into Fact instead of yet another reporting system. Otherwise we're just going to end up with the next architecture problem like transactions, search and custom fields before it.
I see no added value by bringing this into Fact or another reporting system beside the effort to implement this. Provide access to the collected data through common formats (XML, CSV etc.) instead would allow to use any tool to produces any specific report which is needed by the user (see T5151 and T5150).
Actually, I have to agree with merging this into Fact, otherwise we wind up with duplicates of common code.