Hello,
I would like to request that the team considers this again. As a neurodivergent team member, this would be exceptionally helpful to reflect the work I am actually doing. For folks like me, task tracking is often bundled, and at a later time as not to interrupt flow and productivity. Setting a lot of additional reminders renders them ineffective. Is there a practical reason why Asana chooses to omit this as a feature? Could it be something a super user is able to do?
Many thanks.
I have read many of the forum posts about this topic, many dating back to 2017. I would like to bring this back up again. Not being able to correct completed dates for tasks hinders accurate tracking of tasks. Our industry is not always on Asana daily and often do not update tasks until specific meetings to ensure accuracy of the project. Not having this feature has use wondering if Asana is the appropriate solution as we do not have the features for accurate project tracking.
Hi @Greg_Couch , welcome to the forum 
I have merged your post into this existing thread. Don’t forget to vote as you forgot to do so on your original post!
In case it’s not already documented above, you could create your own ‘Completed on’ date custom field (add it to your field library) and have a rule to automatically populate it with today’s date once a task is completed. (and also clear it whenever a task is mark incomplete again).
That way you always have your own completed on field to edit as you wish.
Note to not confuse it with the native Completed on field when it comes to creating charts in Dashboards or Reporting, and make sure to understand such limitations or caveats before proceeding with this approach.
I see that this got marked Resolved, but this is not resolved yet. After using Mondays and Microsoft Project, where you will document Actual Start and Actual Completion Dates, it is hard to not have a similar feature that is then linked to analytics within Asana. Rarely are project tasks marked completed on the day of completion. Typically when the team is together or after the fact, tasks are marked completed and need to be backdated to the actual date. This is especially the case if you are starting new with Asana, and you have a project that is mid-stream implementation, it would be important to have the ability to backdate the “Completed on” date.
Yes, while I can create a custom date field, this doesn’t work well with the project dashboard widgets. “Completed on” is a useful field and should be editable.
Can someone from Asana respond please? Im not sure why this it is taking so long to roll out (since 2017 and now reaching a decade soon?). Ridiculous. it you can create a date to be chosen for the Due Date, certainly you can create the same for Completed Date.
I activated my 14-day trial just to check on this and see if there are any developments. If there are no sustainable workaround on this feature, I will not hesitate to move on to other softwares. I am sure a lot of other users here need this feature as well.
Kind of crazy that this hasn’t been implemented yet. It’s a simple yet crucial aspect of accurate task tracking. As others have mentioned, inaccurate completion dates make comparing expected hours to actual hours impossible
+1 on this as well - Our team performs weekly admin catch-ups (marking tasks complete, sending summaries, workflow cleanup). Because of this cadence, tasks aren’t always marked complete on the exact day the work finished.
We need the Completed Date to be editable so reporting reflects the true completion date. If it’s system-stamped only at status change, it skews cycle time, SLA tracking, and throughput metrics.
While the rationale for a non-modifiable Completion Date makes some sense from an audit trail perspective, clearly there are many use scenarios where a “correct date” is more important than a “toggled date.” At the end of the day, Asana is a tool for the users, so if users have a need to allow for Completion Date edits, it should be implemented. If an org needs a hard audit trail, then consider flagging the field as “modified” and the user that did the edit in the metadata. This is not rocket science. Please add this feature / capability.
adding my voice to the mix. the reasons for this aren’t defensible. every field can have an audit trail, there’s nothing complex about that. and I agree with a few users who have suggested this can be a global/admin on/off setting. this particularly stinks for goal tracking, because if you don’t complete the task on the right day, it throws it off with no fix. and if, like me, you just used AI to import a bunch of completed tasks retroactively, the data is really skewed
Instead of putting the burden on all users to create a custom field in order to better align Asana functionality with reality, why not build both paths natively. Make “completion date” editable and create another field for “date item marked complete”. Further, capture change history (when and by whom) for “completion date” in order to track manipulation of that field. Literally, everybody wins out of the box and users do not have to add this core and clearly desired functionality to every project they create. The wasted time, effort and compute resources tied to the current state are staggering. Respectfully.
I agree with other customers that this issue is not resolved. If using a custom date field does not result in accurate dashboards and goal tracking, this is merely a cosmetic fix and not a functional one. Providing capture of manual change history for the completion date should be enough to satisfy an audit trail.