This would be really useful. We have added a new field for “Security Considerations” to one of our projects and even if it was just filled in with “N/A” when raising the task this would help.
This would be a game changer - I have some fields that are required for people to fill in order for tasks to be routed. It would be great to get this functionality. Also having all Portfolio fields added to the project somehow - we ask people to fill fields in the portfolio view for each project but then this is not visible within the project (I saw this, Can custom fields in the portfolio be visible in the project itself as well - #2 by lpb but it nos really intuitive for the team) - if anyone has a solution for this, please let me know! Thanks
I’m just commenting to keep this one alive. 
I would love to automate certain internal processes after completing a task to eliminate unnecessary copy-pasting. However, I can only do this if people fill in the necessary information on custom fields on the completed task. Hence the need for mandatory custom fields upon marking a task done.
1 Like
PLEASE make this possible! There are so many headaches that could be solved with this feature, and it’s so strange that a tool as robust as Asana doesn’t yet have it.
Need the:
- Ability to identify certain default fields as mandatory
- Ability to identify custom field as mandatory
If it’s an issue of “mandatory for what,” then perhaps there needs to be an option for “Draft” tasks. Then, having the mandatory fields completed allows users to change the task from “Draft” to “Active” or something similar.
7 Likes
Unreal how this has still not been implemented yet get with the program guys wake up ASANA it’s been years!!!
4 Likes
To consider: Depending on what should it be defined as mandatory, based on the project (for project X, custom field A is required, for project Y, it is optional) or based on the task types that were recently introduced (for task type X, it is mandatory, no matter what project it is in). I would prefer based on task type, as tasks are often managed across different projects and this would ensure consistent data quality.
Example case: Task type is “Social Media Post Request”, which puts the task on the current project as well as the process board for the social media team. To ensure the social media team gets all required data to proceed, for this task type a field like “channel” should be mandatory, no matter from which project it was created.