Hello,
Is there a way this custom field will populate the workload chart in the portfolio?
Or is this still only generated from the āAssigneeā field?
Thanks 
Heya Kothar,
Unfortunately it looks like youāve proven my interpretation of the error wrong - then looks like better documentation is needed here because it is unclear how to actually update a āpeopleā field effectively via the API.
1 Like
Thanks Larry!
2 Likes
How do you limit the scope of people that populate the list? I can see the default is org level? can it be limited to only users in a project?
i ran into that same documentation problem and opaque response from the api.
here is my solution: custom_field update value ignored on PUT request using python - #2 by Yoni_Sidi
1 Like
Thanks @Yoni_Sidi , Iāll take a look. Was your example specific to the People field? I canāt tell from your post.
it was general for a custom_field enum value update. the solution is the same for what @Zach_Brak is running into.
This is not an option to my knowledge.
that would be a very powerful feature to define the scope of the field to a project or a team.
Any chance we can get the People options color coded, the way we can with a Single-select custom field?
Hi @mauricio-gp and welcome to the forum,
That seems very unlikely; single-select custom fields have a limited number of possible selections, and those are defined in the custom field builder so colors can be set there. By contrast, the People field is populated from users in the organization; there can be hundreds or thousands of those, and also theyāre not defined in the field builder so the color would have to be set when managing a userās information somewhere.
Hi @Phil_Seeman thanks! Understood. I wonder if it could at least copy from the color that Asana randomly assigns to a userās profile? We are a small team and none of us have profile pictures, so the different colors on Assignees are really helpful.
3 Likes
I donāt know if Asana would implement that, but itās certainly a valid idea IMO!
2 Likes
This is a feature iāve definitely been waiting on! The ability directly in the form to type in a team member and either:
- Assign a task directly to them or
- Add them as a collaborator
Would be huge!
Hi! Iām excited for this field but I donāt see it yet in my domain. Has the rollout been delayed?
You say " By only having one single assignee per task, it creates more clarity around whoās directly responsible for the work, and helps ensure work doesnāt fall through the cracks." But thatās not entirely true!
We are a small team and there are many times a task needs 2 people to work on it, but with one assigned, the other will not see the due date unless they look for it, it wonāt show in their inbox/tasks. Adding subtasks adds another layer of work which could easily be resolved by adding a second collaborator.
The people field does not replace the need for this unless it also allows the person added to get notifications that the task is becoming due. I am so surprised that Asana is so against giving users the choice to add a second assignee if they want to where there is a need - because believe me, there is a need!
3 Likes
Hi @Laura_Moore ,
The people custom field is not meant to satisfy the request of assigning multiple persons to one task. I understand your motives, but by doing that you would lose clarity on āwho is doing what by whenā, that who would not be 100% crystal clear anymore, and trust me, that means issues especially as your team would grow.
There are psychological studies about accountability and how it works that back this approach up.
Also, check out this blog article Why one assignee? as it explains why Asana is taking this approach and (hopefully) wonāt change it.
Cheers,
Rosario
3 Likes
Thanks for flagging this, @Zach_Brak. Our Product team has confirmed that this should now be resolved 
2 Likes