|
[
Permlink
| « Hide
]
Sulka Haro added a comment - 31/Dec/03 02:17 AM
Without reports on the time tracking, the feature is next to useless. I'd love to see good reporting done on the tracking. Please make it possible to view reports for weekly/monthly time periods. Also being able to view a single users time reports for all projects for a given week/month would make JIRA quite usable as a time tracking tool.
Lots of the features mentioned in the original bug have been implemented in the latest release.
Improvements to the reports are on going. User want to be able to filter on component as well as version.
Also they want a time spent report Result would be a report saying how much time had been used that x period. This is a new report as it would have to be implmented differently to the existing reports and the results would be displayed differently. Would be good to pick fields to use for filtering on different reports e.g. timetracking.
We'd like to use time tracking features more too, but we find that they are quite dettached from the general workflow, so it's hard to force users to use them properly.
If users (developers) don't use it properly (log work, put estimates) then the whole results are wrong and the process becomes just a burden. I've found a couple of already logged requests (JRA-1993, JRA-1744, JRA-868...) that seem quite reasonable to me, and would make things easier for users
Another problem we have to workaround is the fact that we sometimes log high-level features that we then split into many smaller tasks, which we then link using a "subtask" link. I'm certain many companies do something similar. The problem is that since for JIRA links are meaning-less, effort estimated on the high-level task won't be kept up-to-date with the effort involved in subtasks, etc. In order to workaround this problem we have to specify quite a complex procedure for our developers. I may log this last problem as a new request. Finally, it's strange that users can log work on open issues, resolved issues and closed issues. I would think that, at least by default, only issues in progress can get work logged (by the assignee). Solving all these issues would make time tracking features in JIRA much more attractive, since they would be less of a burden for the developer (less room for mistakes), and much more reliable for managers. My $.02 This is yet another application of meaningful links. Links should get some functionality tied to it. One would be to combine time tracking data
Added extra issue navigator column that displays ratio of actual work vs original estimate. Also added ability to search against this ratio using a min, max or range query.
I agree with Paco on this one. Time tracking needs to be better integrated in the workflow.
Open: I rarely transition to In Progress for issues that require only a few hours work, so I need to be able to log time on Open instead. Resolved: Time could still be logged for QA or other review work. Closed: I will not bother to reopen an issue to make a quick fix. While restricting when work can be logged might be useful for some, by default it should remain unrestricted. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Make more use of time tracking features
