I’m not sure if this issue was raised but Asana will not roll-up the subtask estimate time when the subtask count is more than 30 (on the List view and even in the task view it errors out with that message of max subtasks reached) which I desperately need fixed to a higher limit. Screnshots below. I review drug shortages as a use case and these are always recurring tasks reviewed at least weekly and can stretch over 1+ years. Ideally maybe 200 subtasks for a max? I don’t really want to duplicate a task and start over from 0 as I then have to merge parameters such as estimate tasks and copy over all notes which is not feasible when the notes can be very long. Also, any templates that are built using more than 30 subtasks will immediately fail to sum which I imagine is a common use case among users. Not sure why the math “engine” on here can’t handle a higher load
I think the equally frustrating part is why this isn’t in the documentation for the feature addition for time tracking. It clearly was planned for and coded for by developers including a very overt alert message. These are the types of details/limitations that MUST be in documentation for any feature rollout so that users can truly assess if they can shift entire workflows to using the new feature. Some of these limitations could be showstoppers to a business workflow and we wouldn’t know until we have spent all the effort embedding a feature into processes that is substantial man-hours to perform. Aspiring to be an Enterprise-level worthy platform requires standard steps such as documentation to be fully transparent and comprehensive. Additionally, when getting involved in Enterprise-grade software universe which by definition has a substantially higher volume of data over very long periods, we must have higher technical limits than those imposed on a thread like this that are more suited for say a small business.
I feel like users are left to uncover these hidden limitations so many times from reading thru the forums.
I use 30+ project templates all with custom fields for estimated time per task; how do I export this custom field data to CSV and then import it to the new Estimated Time field to use with the Asana time tracker?
I’d like to report on the estimated time vs actual time for each task in a project, not just the project’s overall estimate vs actual. And I’d like to export this data so I can dig into it in Excel on a per task level. I have not been able to find a way to do this yet, is it possible?
Is there a way to export the actual time date as well as the timestamp for when actual time is entered? From a workforce planning perspective being able to see via a data export the date time is being entered for as well as when it is being entered would be extremely helpful but I haven’t been able to find a way to see this information.
@lpb Ooh! But… that first link says “It is possible to import and export time tracking values via CSV.” and that’s it. It doesn’t say HOW to export time entries, and I can’t find it. How did you get to it?
If I recall, there’s currently no support for getting to the entries that sum up a task’s or subtask’s time other than in the UI.
Potential workarounds would be to use subtasks (or tasks) for each week’s times (subtasks would be easier because those times roll up to the task level, but I can’t recall offhand if there are any “gotcha” scenarios here to be aware of so test this first if you consider it).
Asana2Go (disclaimer: I’m the creator) offers some flexibility with CSV but not sure that’s necessary or helpful here; depends.