accordingly to timeline, we should able to read the data.
Now: I can find the “estimated hours” under the custom_fields (returns an int that are the minutes), but where/how can I access the “Actual Time”?
Sorry for the confusion here. As @Phil_Seeman said we are behind schedule with respect to API support. We’re working with the engineering team responsible for the time tracking feature to understand what API functionality will be available when. We’ll make a post to clarify asap – thank you for your patience in the meantime.
Hi folks, quick update here: we expect a read API for time tracking to be available by the end of January – we’ve updated the original post to reflect this.
To further clarify: as @Stefano_Tranquillini mentioned above, Estimated time works as a numeric custom field that you can read and write, with the value representing a duration in minutes. Actual time will be a new property on task objects available for reads but not writes (until later in 2023).
We’ll let you know when the API is available via the forum and update the our API documentation with the details. Apologies once again for the confusion.
Asana-created custom fields include an asana_created_field identifier
It is now possible to read time tracking information for tasks in the API! Additionally, we have added an asana_created_field field to Custom Fields.
Actual time: the actually recorded amount of time it took for a task to be completed.
available as the actual_time_minutes on the full Task resource.
this is a read-only sum of all time tracking events for this task
Estimated time: the time that was estimated by a user for the completion of a task.
available as a number custom field in the following endpoints:
Estimated time fields will include asana_created_field: estimated_time
Asana-created custom field: special custom fields available in the Custom Field Library that are made by Asana and feature the Asana logo badge.
when a custom field has the asana_created_field field set to a non-null string, it means this field appears as an Asana-created custom field in the Custom Field Library
you can modify the values in these custom fields
you cannot add a field with asana_created_field set
you cannot delete one with asana_created_field set
You may notice that it is possible to modify the estimated time values with this schema, but not the actual time values. For the moment, while it is possible to modify the estimated time values, we have not locked down the specification for how that affects Time Tracking. In other words, you may update the estimated time values at your own risk.
That said, we’d love to hear your feedback on that functionality. Stay tuned in the future as we continue to add more API functionality for Time Tracking!
Original time tracking non-API launch
First API launch and announcement
Yours in Developer Relations,
Sasha, on behalf of the Asana API Team
Thanks @sasha_f . Are you planning to implement individual entries as their own API items or is there any way to get this now that I’m missing? We have multiple team members work on one task; we are a creative agency so, for example, 30 minutes from an Art Director and then 4 hours from a Designer is currently represented in the API as simply “270 minutes” total, but we bill for the hours worked by these two people at different rates so the information is only helpful to us if we can delineate.
At this point in time, only a sum of the actual time is exposed via the API. However, were are definitely interested in expanding the functionality to include all of the individual entries exactly as you described. I’ll share your use case with the team that’s working on this, and hopefully they can prioritize it!
Thank you @sasha_f - I would appreciate you letting me know here even a vague idea of timing as soon as you know, as we have avoided paying for and implementing a secondary time tracking tool in anticipation of this feature and were counting on the API read functionality supporting this by the end of January, so it’s a hot issue for us! If it’s only a couple of weeks away we can wait, but if it’s likely going to be months or more we need to find an alternative ASAP. I appreciate you looking into it for me.
I would like to receive reports on the current time for employees in the API. What tasks did they work on today and how much time did they spend on each task.
Now we use Everhour for this, adding this information to the API would allow us to go completely to the functionality of Asana
Are you planning to add the ability to implement a timer in the project rules? For example, when a specific field is changed, the timer would start at the same time, and when the field is changed to other option again, the timer would pause? Currently you can only add timers via the information textbox and you can’t edit, rename or set the just mentioned rules, which is quite limiting and the potential what can be use is in the new feature, unfortunately I can’t use yet.
Hearing you loud and clear. I’m working with teams internally to adjust the priority of exposing finer-grained data via the API. I don’t have a timeline I can share yet, but the moment I do, I will update this thread.
Thanks for the useful thread. As many people, I also need to compute the cash burn base on timeline. Indeed, I need to track traversal tasks like “intern call”. The stake of time tracking according to me, it’s to identified project that will go out of the budget (in terms of human days) and daily duty that take time and cost money to the company.
With those kinds of details, we could have good discussion like doesn’t it normal that we spend more time on “intern call” this month.