Required field to be filled in before allowing a task to be "completed"

I couldn’t agree more. This is critical in operations.

This would be really useful for us. Many developers forget to specify a resolution when closing tickets which makes tracking this as a data point very difficult

To kinda solve this situation, our tool Asana Pulse allows you to define custom searches + expected result. The tool will run those searches everyday and compare the number of results to the expected. For example you could say you expect 0 tickets completed without a positive point value, and the tool would inform you every day.

Hello team,

Do we have any resolution to this yet?


1 Like

Is it possible to create fields that are mandatory to fill in before you can mark a task complete?
We have several tasks that “Mr. another person” always forgets to fill in the required text in fields and they complete the task with missing field description. We are trying to integrate it, but it would be nice to not be able to complet the task before this was executed, everybody will quickly learn the reason why they cant complete the task, and fill in the required field text.


This is definitely a must to have feature for many of us. I am also eagerly waiting for this option. Asana team is there any update on this ?


No news given on the forum, and Asana does not communicate on the roadmap.

We need this Asana!!!

1 Like

Would love required task fields. Also would love if the asana asana was public haha

The Asana roadmap you meant?

This is an absolutely necessary, and one that could convince me to upgrade if it was available. I understand their open philosophy (I’ve been using Asana since 2012) but since my career has evolved and I’m much more on the planning side of things now, I recognize that pretty much every manager does some cat herding. Putting up some fences to keep things moving in the right direction is necessary.


In our case, we have a certain kind of tasks (tracking prod issues) which require sharing several pieces of info upon completion. Currently the workflow in the engineering team is as follows:

  • an engineer resolves a task
  • an Asana workflow creates a subtask assigned to John Smith (always the same person) that asks to fill in a linked spreadsheet: create a new row that corresponds to the resolved task and provide several pieces of info like the root cause, what kind of impact it was, how apparent it was to the customers, and ideas for a long-term fix
  • a script that uses Asana REST API scans over the backlog of subtasks described above (they have a well-defined title, so it’s easy to find them) and reassigns them to a person that is most likely to provide the required info, currently it’s the resolved ticket’s assignee
  • the person gets the subtask assigned, needs to fill in the spreadsheet and resolve the subtask

Even though the amount of data needed to provide for each task is minimal, the process feels heavy because it’s kinda asynchronous. If we had a way to provide this info strictly upon resolving a task in Asana, we would keep the engineer’s focus and benefit from fresh memory after the incident.

I’ve seen that Asana has a feature of using forms to create tasks. We could reuse the mechanism of forms so that it appears when a user tries to resolve a task: display the form, collect required info, map it to the task’s fields, and once the form is complete and sent, do resolve the task.


THis seems like a very basic request. Not sure why it isn’t being implemented. As the operator af the business i need to make sure everyone is adding tags to tasks so that we can organize them. If someone fails to tag an items the item is essentially lost. Also forcing fields in general should be an option. Thanks so much.


We have an automation incorporated to our ASANA. Certain tags added to a task automatically email clients. My team sometimes forgets to put email addresses in a certain field and then email can not trigger. Which causes errors in my automations. I would like to be able to make certain fields mandatory so my team does not forget to put this information in.

I vote YES on this request as well.

1 Like

We upgraded Asana and this feature is something we really need- we have considered other platforms over it. We will never eliminate human error but it helps to have required fields to avoid simple mistakes- they happen. Is there any update on when this feature would be available as it is something we would need to keep using at Asana.

Welcome to the Asana Community Forum @Natasha6 :wave:

A workaround with rules might help

Hi Asana folk. This request has been out there for three years so I’m adding to the list of loud calls for mandatory project fields to become a feature. Enabling certain fields to be required allows organizational standards to be conveyed and enforced, and work metrics to be tracked consistently. Metrics and standards cannot be supported if key data points are not prominent.

Required fields have been commonplace on digital products for decades, and are commonplace even on paper products. This request has nothing to do with limiting creativity, but rather building discipline towards a standard by allowing teams to see which fields are required and which are optional.* Without such an indication, everyone interprets differently which fields are most important.


(*It’s rare that every field may be required all the time on a project. Personal discipline and organizational guidance is necessary to ensure required fields are reasonable in type and quantity.)

1 Like

This is kind of a critical feature for time tracking. Users are typically pretty good at putting in an estimated time when creating a task, but tend to forget to update the task with actual time when marking it complete so having the platform for that would be great.


Is there any update on this feature ?
No useful statement from asana since more than 3 years. Very annoying

Welcome, @Oleg_Kryschanowski,

Forum threads are updated when there’s new information, but not otherwise, because of both the volume of threads and because Asana, like many products, doesn’t publish a roadmap.



1 Like