In order to fully take advantage of the workload portfolio view, you’re required to have estimated times associated with tasks on relevant project boards. However, there seems to be no way to automate this entry with rules. When trying to create a rule, you can leverage custom fields with dropdown options but neither a custom field with number format nor the Asana-created field for estimated times can be used for a triggered action. This is prohibiting accurate visibility of team capacity as it relies on individuals manually inputting these times themselves (which doesn’t happen).
I agree. There is an opportunity here to help create the proper habit.
I believe forgetting to add time estimation or to start a timer is probably now one of the biggest bottlenecks for more accurate time and workload tracking. i.e., the fact that we are human is the bottleneck. 
I thought it would be great if a rule could be set to remind people to add time estimates if the field is empty, maybe with one click from My Tasks, kind of the same frictionless UX developed for adding the Time Tracking Custom Field.
2 Likes
Just replying to add more weight to this. Seems kind of crazy to not be able to create a rule that enforces users to add estimation in a Task/ Story or it won’t be allowed in To Do. For those (like me) that operate this way that is.
I was also in search of whether it was possible to automate estimated time when a task is created. I agree with what @Fraja_Hodges mentioned about taking advantage of the workload portfolio view. I have an approvals pipeline set up where tasks get created from a form, and I would like to have an estimated time included when that task is created, but there is no way to automate that. The estimated time would have to be added manually after the task is created, which is an extra step that our editors can easily skip.
Asana, please add this feature!
3 Likes
The fact that ‘Custom Fields’ cannot be filtered like a dropdown in rules when they are text and number based is indeed a problem in managing workflows. Therefore, I have prepared a rule that allows you to do this. I think it will solve your problem for the ‘Estimated Time’ case. If you are interested, the forum post where I explained the feature in detail is here. Or you can ask me directly, I would be happy to help.