SEE ALSO:
- Reports based on Time spent
- Detailed Time Reports for Hierarchical Entities
- Tabular Report with Detailed Time List: add Custom Columns based on Metrics
- Detailed Time Spent reports by User Story with Tasks and Bugs
- Detailed Time Spent reports by Feature, by Epic, by Portfolio Epic
- Detailed Time Spent reports by Work Item with Relations
- Detailed Time Spent reports by Release, Iteration, Team Iteration
- Detailed Time Reports
Brief summary of this article:
With Time Tracking practice enabled, Targetprocess users post actually spent time against various entities. Detailed time reports are based on Times data source and operate with lists of time spent records. This article describes data fields of Time entity.
Use the fields to filter lists of time records. Group the records per work items, work scopes, users, roles, and date ranges. Calculate totals per each sub-group.
Predefined Fields
Spent, Remain
Spent field is a key value field. It contains number of hours a user submitted as actually spent. Calculated read-only Time Spent fields in work items are permanently updated with sum of Spent values (in actual hours) taken across all Time records attached to the work item.
Remain field is a manually input forecast. Users made their forecasts at the moment when they submit the records. In Time records, remain values are not updated retroactively. They are preserved for history tracking. Calculated read-only Time Remain fields in work items are permanently updated with the most recently provided Remain values (in actual hours) taken from all Time records attached to the work item.
Time Spent and Time Remain values for a User Story include sum of time spent / time remain values both of the User Story itself and all its nested Tasks.
More on this: How is Progress calculated for work items: User Stories, Tasks, Bugs, Requests.
Description
Description field contains text descriptions users provide to every submitted time record.
Date, Create Date
Date and Create Date fields contain timestamp values. Learn the difference between these two fields. Date refers to the date the record is submitted against. Create Date refers to the date when the record was submitted. Say on Friday evening (Create Date) users may submit time records for all the past week from Monday till Friday (Date).
Grouping and filtering by Date field is done in time reports with distribution per week / month / quarter / year.
Entity References
Assignable, UserStory, Task, Bug, Request, TestPlan, TestPlanRun, CustomActivity fields in each Time record refer to a work item or an activity the record is related to. Project field has reference to the Project that contains the work item or the activity.
User Story field is not blank only when a Time record is related to a user story directly. When a record is related to a Task or a Bug having a parent user story, the User Story field in the Time record remains blank.
Grouping and filtering by these fields values is done in time reports with distribution per work item. Examples:
Time Spent per Feature, Epic, Release, Sprint, Team Iteration
There are no prefefined fields displaying references of Time records to high-level planning entities. To build time reports with distribution per these entities use custom calculations based on custom formula metrics or Visual Reports calculations. Examples:
User
User field in each Time record refer to a user the record is related to. Usually it is the user who submitted the record. However power users with sufficient Role Permissions are able to submit Time records on behalf of other users. More information: How to Grant Access to Other Users’ Timesheets.
Role
Role field in each Time record refer to a related Assignments Role. The field is used when for the same work item Effort is estimated for multiple roles separately, for example, Developers, QA Engineers, and Designers. A user may be assigned to the same work item under multiple roles, and submit time spent on behalf of each supported role. It helps to provide Spent and Remain values per role, and track progress of the work item per role as well.
Full list of predefined fields is available here: https://md5.tpondemand.com/api/v1/Times/meta.
Custom Fields and Custom Calculations
Custom Fields contain extra details on each Time record. For instance with these fields it is possible to: track Billable vs Non-Billable records, or multiple types of activities. Custom Cost values can be calculated per each Time record using custom rate values. Examples:
- Tracking Billable and Non-Billable Time Records
- Budget Spent Reports with different rates by activity type per Project
- Detailed Time Cost Report
- Tabular Report with Detailed Time List: add Custom Columns based on Metrics
See Also
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.