JayLing
Summary:
The Filtered Team Tasks endpoint (GET /api/v2/team/{team_id}/task) with the list_ids[] filter only returns tasks whose home List matches. Tasks that have been added to a List via the Tasks in Multiple Lists ClickApp (home List elsewhere) are silently excluded. Please add a parameter to optionally include these location-associated tasks.
Current behavior:
  • GET /team/{team_id}/task?list_ids[]={listId} → returns only tasks whose home List is {listId}.
  • A task whose home is List A but is added to List B does not appear when filtering by List B, even though the task object's locations[] array clearly lists B.
  • The per-List endpoint GET /list/{list_id}/task does include explicitly-added tasks, but it can't filter across multiple Lists, statuses, assignees, or date ranges in a single call the way the team endpoint can.
Requested behavior:
Add a query parameter (e.g. include_lists_tasks=true or match=location) to the Filtered Team Tasks endpoint so that list_ids[] matches a task if any of its locations (home or added) is in the filter — consistent with how the UI shows a task inside every List it belongs to.
Use case:
We run release automation that pulls every task in a sprint List with a given status (e.g. "Ready for Release" / "In Release") to cross-check against GitLab merge requests. Teams frequently add (not move) a task from a project List into the current sprint List. Those added tasks are invisible to our query, so release-bound work gets silently dropped from the audit. Our only workarounds today are (a) forcing everyone to move instead of add, or (b) querying every possible home List and fetching each task's full detail to inspect locations[] — expensive and brittle.
Why the team endpoint specifically:
We need the combined filtering (multiple Lists + statuses + assignees + due-date range) that only the Filtered Team Tasks endpoint provides; the single-List endpoint doesn't support those combined filters, so we can't simply switch to it.