Does Asana have a native capability to differentiate between end dates and due dates?
Example, i have a task that starts on Monday 15th, it is due on Thursday 18th, but will now take 4 days, so the end date will be 19th.
Start date is 15th
Due date is 18th
End date is 19th - the task will be 1 day late with no intervention.
Asana treats End Date and Due Date as the same thing, unless i am missing something ?
I would normally set this up so that only Milestones have Due Dates - those are the hard deadlines you have to hit.
Tasks and sub tasks would have end dates.
Project Status then shows as behind or at risk where End Dates > Due Dates
Is this possible ?
4 Likes
Hi @Nick_Christy I usually use the due date as the end date but I add a custom date field for original due date (baseline)
1 Like
@Nick_Christy I am wondering if you were able to address this. We are currently looking into this very thing during our Asana trial. (Our existing tool has the feature of only milestones have due dates and each milestone also has a projected end date, based on the remaining durations in the chain leading to the milestone. It allows us to quickly compare, in a proactive manner, if you are on track or not.)
The closest thing I’ve thought of thus far is creating custom fields (1) calculating remaining chain length to then convert into (2) a projected end date for milestones, then (3) make project health/status a formula which is dependent on “how late” or “how early” we are to milestones.
1 Like