| Reporter |
Ryan (Walsh)
|
|---|---|
| Created | Jan 23, 2013 10:48:27 PM |
| Updated | Apr 4, 2013 4:40:00 PM |
| Priority | Normal |
| Type | Feature |
| State | Open |
| Assignee | Pavel Nikolaev (pasha) |
| Subsystem | Time Tracking |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | 4.1.2 |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
Timetracking in 4.1 - very impressed. It's ALMOST exactly what we're looking for. If only it had ONE more field when entering in time
TYPE
With a field "TYPE" I could distinguish time spent in a report for SPEC WRITING, QUALITY, DEVELOPMENT etc.
This will allow project managers to see if we're over budget, under budget, etc. Right now, all time is added together in your reports, so I can't tell if it was development quality, spec writing, etc.
TYPE
With a field "TYPE" I could distinguish time spent in a report for SPEC WRITING, QUALITY, DEVELOPMENT etc.
This will allow project managers to see if we're over budget, under budget, etc. Right now, all time is added together in your reports, so I can't tell if it was development quality, spec writing, etc.