Inconsistent handling of custom fields in Search API vs. Asana UI Search

[Uli.Kisslinger]

We’ve encountered an inconsistency between the Asana Search API and the UI search, specifically around filtering tasks by custom fields of type People.

When calling the API with the following endpoint the parameter custom_fields.{GID}.value={GID} is ignored when used for a custom field of type People:

https://app.asana.com/api/1.0/workspaces/{GID}/tasks/search?projects.any={GID}&custom_fields.{GID}.value={GID}

In the UI search, however, the equivalent query works, but it uses custom_field_{GID}.selected_people instead of value.

The API documentation doesn’t provide details on how to filter by People fields, nor does it clarify the difference between value and selected_people. It also lists unsupported cases like multi-enum, but doesn’t mention People fields at all.

Currently, we need to:
1. Fetch a larger set of tasks (e.g., all tasks from a project).
2. Apply filtering manually on the backend.

While this works, it is resource-intensive and becomes slow with higher task counts.

Has anyone figured out a proper way to query People custom fields via the Search API?

Is there a parameter or syntax we’re missing? Or is this simply not supported right now?

I’d appreciate any insights on this topic. From a developer perspective, the API/UI inconsistency feels like a bug — or at the very least, a missing feature that would greatly improve usability.

[Phil_Seeman]

Since people fields work very similarly to multi-enum fields and the latter is not supported by the API search, I’m not surprised that people fields would also not be supported. But I’ve pinged some Asana contacts to hopefully learn more.

[dbrdak]

Hi Uli!

@Phil_Seeman is right, people custom field is a special kind of multi_enum field which is not supported in this endpoint. Also, I can’t see it in our API Roadmap, so it will likely not be supported in the nearest future.

That said, if you find implementing this feature useful, I encourage to make use of our form, where you can submit new enhancement requests for the API.

Thanks,
Dominik

[Uli.Kisslinger]

Thank you, Dominik. I will use the mentioned form to submit this as an enhancement request.