Knowledgebase
Search the Rally Knowledgebase to find solutions to your Rally product questions.
How To
Time Tracking allows Rally users to use one interface to enter hours daily while updating their development status and provide managers with detailed timesheets for software capitalization and billing reports.
Time Tracking alleviates the double entry issue developers experience when their organizations require them to fill out weekly or monthly timesheets. By capturing timesheet entries in Rally, Time Tracking saves developers' time and collects more accurate project cost estimates by recording daily hours spent on development work.
Some of the benefits of Time Tracking include:
-
enter hours per day on a task, on a defect, on a story or on a Rally project
-
enter hours retroactively
-
multiple users can enter time against the same task, defect, or story
-
navigate to prev/next week in timesheet view
-
add/remove existing Rally task/defect/story/project as a timesheet entry
-
view daily and weekly totals
-
view and update tasks ToDos from timesheet
-
personal timesheet report (PDF) for current or past week
-
automatically populate timesheet with tasks owned by current user
-
scope timesheet content to the current workspace
Additional Information
Comments
Time spent working on the Story entered on the Timesheet page is not updating actual time for the Story or Task.
Hi Igor,
I see you also opened up a formal support case with us around this issue, and we explained the differences between the two fields.
If anyone else in the community has this question, please note that the actuals field does not link in any way to the Time Tracking functions inside of Rally. We are currently developing a new field, Time Spent, which will aggregate any entries across a subscription to show total hours entered in the Timesheet by those working on said task/defect/user story.
Please let us know if you have any additional questions,
Kyle
Hello Kyle,
Do you have an ETA on the new functionality? The way it works right now makes not much sense.
Thank you,
Igor
Igor,
While I don't have any formal ETA's, I can tell you it's near the top of the applicable dev team's backlog. Since we've began a shift of our development to a pull-flow model, we can begin work on the next item as soon as the current one is completed. To get an idea of what our next items in current development are, please check our work in progress page here - http://agilecommons.org/pages/c11b1b38a3.
Regards,
Kyle