Asana API `request.enum_added` findings

Specification revisions captured on 2026-09-28 UTC.

Revision `71527e3c9eed`

Capture ID rel_388a20151c424ff7d15e7c78b40984e1558b2b57092beda2e37b7105c93b25a1

Previous specification SHA-256 87288c59f5ea5974980f0916b190043429deab33aac6aa8c38635f88ac816a6d

Captured specification SHA-256 71527e3c9eed5d75e3fe323d34c00f6b3422486c8fce44d085859fc484bf939a

108 recorded findings in the release. The published snapshot contains the first ten findings.

non breaking POST /projects/{project_gid}/duplicate · items/
added the enum value `dates_rollup_progress` to the property `items/` of the `query` request parameter `opt_fields`
non breaking GET /tasks · items/
added the enum value `has_subtasks_date_mismatch` to the property `items/` of the `query` request parameter `opt_fields`
non breaking POST /portfolios/{portfolio_gid}/duplicate · items/
added the enum value `dates_rollup_progress.updated_tasks` to the property `items/` of the `query` request parameter `opt_fields`
non breaking POST /tasks/{task_gid}/duplicate · items/
added the enum value `dates_rollup_progress.updated_tasks` to the property `items/` of the `query` request parameter `opt_fields`
non breaking POST /projects/{project_gid}/saveAsTemplate · items/
added the enum value `dates_rollup_progress.total_tasks` to the property `items/` of the `query` request parameter `opt_fields`