I’m looking for a way to create a required field across all my Asana tasks and projects that allows for two different deadline fields. The way we work at my company requires distinguishing between:
Request Deadline (Final Due Date) – The date when the task needs to be completed or go live.
Work Deadline (Internal Task Date) – The date when I need to start or complete my part of the work before the final due date.
For example, if I need to send an email on March 1 the requester will set the task due date for March 1—but if I only see the task on that day, it’s too late for me to work on it. I actually need to create and schedule the task to work on it by February 26, but if I change the due date for Feb 26, it is not clear if it is the date I will be working on it, or the day the email will go live.
I’d love to know if there’s a way to make these two fields required across all tasks and projects to avoid confusion and ensure proper workflow management. Any suggestions or best practices?
This is the exact reason for not sorting or grouping your My Tasks by Due date but rather by an approach more along the lines of my often-used article:
I’d recommend you and the others at your organization use Asana this way as a best practice rather than what you’re asking to do, which will be more effort and less effective, I believe.
But since you asked, you can’t actually directly require fields everywhere. If you are on Enterprise you could use Bundles to accomplish this, otherwise you have to make sure every project uses the fields you want. I’d recommend you treat the built-in Due date as your Request Deadline and just make sure you add one custom date field, Work Deadline, to your org library of custom fields and remember to add to all projects. You could also create a project template with that field built-in, and try to only create new projects from that template as an effective way to ensure all projects have that field.
Also, may I move this topic out of this private category so 800k+ others can benefit from it?