RTC Custom report for time spent by user, by task and by month
A customer is using the Scrum template without adding the "time tracking" functionality from the Traditional Formal Project Management template. They would like to create a custom report showing the activity (time spent) by each user and by task per month (not by iteration). As users will use the time spent attribute to input time spent each day, there is not a detailed info of the time dedicated by day (only through searches in the detailed history of the WI).
As far as I know, the DW WI tables store the total time spent value for each WI but there is not detailed info of when each time addition was entered by the user, so I don't have this info to create the detailed report. Is there something I am missing and could this info be extracted from other WI historical tables or the only info available is the total time spent by each WI but not detailed inputs for this attributes with corresponding timestamps by user and date?.
If customer uses the traditional template and WI time tracking, could this detailed monthly report be created?
Many thanks,
Ana
2 answers
Comments
This is exactly - the monthly report - what my customer asks for!
In addition she wants to enforce each developer to report every day the time spent on a task (so a user can say I spent 3 hours, or 0 hours on a task), but wants a report that shows if a developer did not report on each day.
Yes they want a very strict timely reporting system, based on the Time Spent value, with or without the Time Tracking entry. Any more ideas?
Thanks!
If you would like to check the time\day of entering timesheet entries - it's possible during save work item action only (no such data exposed for BIRT).
Does anyone want to share the BIRT template for such a report?
I looked across the databse of RTC to find historical data of the time spent but I don't found where this information is stored.
I need help. Someone has an idea or solved the problem ?
Comments
We solved it by adding the time track tab to Scrum template and leveraging RPE's powerful capabilities for REST reporting. It's a lot of work, but we needed in a POC situation last year..