Number formatting of "estimated time" in charts in hours instead of days

Please, please can this be addressed. Who on earth thought time format in 24hr days was a good choice? Who works this way?

How hard can it be to change this to decimal?

4 Likes

Great work around, but this new field that is created is not supported by the ā€œTime entered dateā€ filter

5 Likes

This workaround is ridiculous. Are we expected to pay for Asana Business and also make a common sense time reporting workarounds for every single project. Will Asana reimburse us for the time it takes to implement this across 28 projects? This is not difficult developmentally to always show time in hh:mm format, thatā€™s it. Itā€™s 2 lines of code.

4 Likes

Hi @Anastasia_Golovko , seeing you are new to the forum (welcome :wave: ) you may not realize that I donā€™t work for Asana - Iā€™m a volunteer forum leader and an Asana Solutions Partner that helps people make the most out of Asana, including such workarounds to get over any road blocks and work with what weā€™ve got.

I also agree with you, clearly the majority of businesses work in hours and I would also prefer to see the charts in dashboards to display as such by default.

Remember to click on the purple vote button at the top of this thread - thatā€™s how you can really make your voice heard.

Thanks!

3 Likes

Would be much more useful to show reporting in number of hours vs. grouping in 24 hour days/7 day weeks. Please fix!

Hey @Lindsay_Killian , appreciate your frustration but did you try this?

Tracking time for team members could be so easy in Asana if they just updated the way time is shown in reports. The default right now appears to be showing time in 24 hour day increments, which is deeply impractical. If the default was changed to just show hours totals it would be more usable. Or, preferably, this field could be made editable to choose the definition of a Day to fit the standard work day for each team.

2 Likes

Agreed, having the same issue on my end. Asana please fix this!

1 Like

@Tanya_Willhite-Vaugh , @Rachael_Conti (welcome to the forum :wave: ),
Iā€™ve merged your posts into this thread - make sure to check out my workaround here.

What is the actual formula? Iā€™m not a coder, so the image you inserted in the instructions just shows #Estimated time, but it seems linked to something? A formular that is hidden maybe? What do I enter here exactly?

Hi @Katie_Fleming_Dahl , welcome to the forum :wave:

If you go to the Customize button in the top right area, under Fields, add Time tracking fields (Estimated and Actual time). These will now be available as Inputs in the advanced formula editor.

You can also just type ā€˜Estimatedā€™ without the #

The day roll up is crazy, the week roll up is chaos.

The default time tracking should simple calculate the total estimated and actual times in hours.

I think this topic should be alive even though weā€™ve got workarounds for it.
I believe in the default formatting should be in hours(or hh:mm).
Or I want to select a formatting from some choices(ex weeks:days,hh:mm,hh,mm and etc).

The advanced editor for formulas should be used for more user specific needs.

2 Likes

Bumping this thread as well! First time posting, but the current process is unhelpful at scale, so the ā€œfeatureā€ is being gated behind a paywall, which isnā€™t necessarily accessible to all users (even though hour tracking is much more standard than day/week tracking).

Hope this can get updated to accommodate users not on the premium plans :pray:

1 Like

Agreed that hours and weeks is madness. We need hours please!

Keeping this thread going. It would be great to get this resolved soon. Such a pain for time tracking!

I cannot believe that this thread is going since Jan 2023.

And thereā€™s a marked ā€œSolutionā€. The person that suggested the fix started with: ā€œThis is not a solutionā€.

1 Like

Hi @Thomas_Pessato , that person would be me. And Iā€™d like to believe there is no problem with me or other volunteer forum leaders that have agreed to use this convention to elevate key replies / workarounds, which appear to have helped numerous people.

Thanks!

3 Likes

Hi @Thomas_Pessato

This is a common convention in most community forums. As @Richard_Sather pointed out, marking an answer as a solution helps bring visibility to the most helpful response, which often benefits others seeking the same answer.

Please remember that product feedback posts typically focus on suggestions for improvements or new features, rather than issues or bugs. I understand it can be frustrating when changes you feel are simple arenā€™t immediately addressed, but feature development takes time and must be carefully evaluated by the product team to ensure it aligns with overall goals.

Lastly, using all caps is generally interpreted as shouting in online communication. Iā€™ve edited your message, as Iā€™m sure that wasnā€™t your intent toward other users trying to assist you.

Thanks for understanding!

1 Like