@Richard_Sather for the first example in section 1. — is there a way to display just the whole number of days? so the same day it’s created = 0, the next day it would equal 1, etc ?
Hi @Matt_Horan , welcome to the forum 
So you would like the result formatted to a whole number without the hours or decimals? Unfortunately, currently, there is no way to remove the hour or have the decimals round up/down to the nearest whole (day, in this case).
Hoping that number formatting will be added to formulas fields by the Asana team, at some point, soon! 
@Richard_Sather Correct!
The 3 biggest opportunities, in my opinion, when it comes to Dates in Asana are:
1. Formatting - I’d like to choose how precise the displayed value is, just like in Google sheets when working with dates.
2. Conditional Logic - some fields only make sense to calculate once a certain condition is true (for example: I only want to populate the “Days to Solve” field once a ticket is marked as Complete).
3. Workdays - we need a way to define what days are workdays for our teams and switch between Days vs. Workdays (this is a well establish concept and there have been built-in formulas in Google Sheets for 10+ years). Without that, if my team doesn’t work on Sat/Sun, it would look like a task created on Friday afternoon and solved by EOD Monday took LONGER than something created on Monday and solved Wednesday (3 days vs 2)
Happy to put these in a separate feature request thread, but other ideas related to the concept of the TODAY input and Advanced formulas.
- Days in Status - when I hop into a board view, I want to be able to immediately see if anything has been sitting there for longer than I’d like it to. This is a fairly standard feature in JIRA & Trello. Right now to do that I’d have to click into each task, scroll to the bottom to the Activity Log, parse through the updates looking for the date it was moved into the current section, then do the math to figure out how long ago that was—which means, it will never happen.
- Ticket Age - it’s surprising to me that I had to make a custom field to capture this information. I’d expect a standard metadata field would be available for me to add to card and task detail views so that again I can avoid going through the steps outlined above just to understand how long something has been here. Even with the Created On field showing in list view, let’s not make people do math subtracting those values against today’s date over and over for each row—let’s let the computers do the boring stuff
Hi @Matt_Horan , great suggestions which I agreed would be definitely useful.
I would also encourage you to post these in separate threads in the Product Feedback category, although I’m fairly sure some of them may already exist so have a good search, or look out for the suggested similar posts on the right of the post editor, once you start typing your thread title.
Here are some tips to some of your points.
-
Formatting has to do with the decimals set in the number fields that are included in a formula, so you can have some control, but clearly not fully, such as rounding up.
-
Conditional logic - you can have a ‘placeholder’ number field that is populated once a rule is set. In your example you can have a (hidden) formula field called “Days to solve (incomplete)” which is automatically calculated (based on completed on minus created on). Then have a simple number field called “Days to solve” which gets populated (with the same value of your formula field) once the ticket is marked complete).
-
Workdays, Asana has recently introduced Project customization and views. This will affect the data in charts (as I describe in my next point, below) but will no affect formulas, which is still an issue. For tickets that are open over several weeks, you could multiply the value by (5/7) so you get an value closer to 5 workings days, rather than 7. It works for some, but still not entirely accurate.
For what it’s worth, regarding your Day in status bullet point - you can actually extract this information using a chart in a dashboard, but you will get either a total or average, not for an individual task.
Plus, you can format the count as you like:
Hope some of this helps!