# Change many tasks at once: reschedule, reassign, rename, close or groom

> Change many tasks at once: reschedule, reassign, rename, close or groom: 0 companies fully do it, 18 with a limit, 20 carry the tag. Every listing in Project & task management with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/project-management.update-tasks/
- Markdown: https://www.anchorterminal.com/niches/project-management.update-tasks/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/project-management.update-tasks/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/project-management.update-tasks/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 18 | 20 | 12 | 7 |

## What counts as done

Every targeted task changed and read back with the new value, a per-item failure list for any that did not change, no field silently dropped, and recurrence preserved unless asked otherwise.

How agents ask for it: push everything due today to Monday; reassign Ana's tasks to Tom; close all completed tasks; groom the backlog and fix the labels

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Asana (Asana, Inc.)**: update_tasks changes up to 50 tasks a call and reports successes and failures separately, but acc-42 shows a timed due date dropped with success-shaped output, and recurrence handling isn't documented.
- **Basecamp (37signals LLC)**: PUT /todos/<id>.json and completion endpoints change one to-do a call with no batch endpoint, and acc-31 shows archiving through the agent hiding comments the web app cannot show.
- **ClickUp (Mango Technologies, Inc. DBA ClickUp)**: task.update_many applies one shared change to named tasks, so per-task values like different dates need one call each; clickup_update_task returns only id and URL, and acc-32 (community server) saw success with nothing persisted.
- **Financial Cents MCP (Financial Cents LLC)**: manage_project_task updates one task a call, omitting unchanged fields; no bulk update, and the response carries only id, title and board, so a re-read is needed.
- **monday.com (monday.com Ltd.)**: change_item_column_values sets several columns on one item a call; no batch tool, and acc-26 saw 6 of 12 updates fail with Item not found when ids went as floats.
- **ONES (The Beautiful ONES Technology PTE. LTD.)**: update_issue and execute_issue_workflow change one issue a call; no bulk update tool is listed and the response shape isn't documented.
- **OpenProject (OpenProject GmbH)**: update_work_package changes one work package in place a call with lockVersion conflicts returning 409; no bulk update tool.
- **Plane (Plane Software, Inc.)**: workitem update changes only the fields passed, one item a call; cycle transfer_workitems moves unfinished items in bulk, but there is no general batch update.
- **Redmine (Redmine project)**: PUT /issues/<id> changes one issue a call; no bulk endpoint, and errors other than validation failures return a status with no body.
- **Roma (Milo Mode Inc.)**: update_items changes up to 200 items a call with per-item titles and values, but status and due date apply to every item in the call, and batches over 20 entries queue as a job to poll.
- **Shortcut (Shortcut Software Company)**: PUT /api/v3/stories/bulk applies one change to many stories in one request, but per-story values need separate calls and a per-item failure list isn't described.
- **Taiga (Taiga Cloud Services, S.L.)**: PATCH changes one object a call with its version for concurrency; bulk endpoints only reorder or move items between sprints, not change fields.
- **Taskade (Taskcade Inc.)**: Separate tools set dates, assignees, notes and fields one task at a time; no batch tool, so 50 changes are 50 or more calls.
- **Teamwork.com (Teamwork Crew Limited)**: update_tasks, complete_tasks and move_tasks batch changes with per-item results, but whether the response echoes stored values and how recurrence is treated aren't stated.
- **Todoist (Todoist Inc.)**: update-tasks, reschedule-tasks, complete-tasks and manage-assignments take many tasks, but update-tasks replaces the due string and removes recurrence, so the agent must pick reschedule-tasks for dates.
- **Trello (Trello, Inc.)**: PUT /cards/{id} changes one card a call; /batch takes up to 10 GET requests only, so 50 changes are 50 calls.
- **Wrike (Wrike, Inc.)**: update_items applies the same change to up to 20 items at once, so different dates per task, or 50 tasks, need several calls; REST POST /batch takes 100 operations.
- **YouTrack (JetBrains s.r.o.)**: update_issue changes one issue a call; no bulk tool in MCP (the REST commands endpoint applies a command to several issues, not read here).

## What stops agents finishing

- update returns success while dropping the field
- no batch endpoint, so 50 changes cost 50 model turns
- archive or delete semantics differ from the web app, so humans cannot find what the agent removed

## Around it

Before: project-management.find-work. After: project-management.status-report, messaging.post-update.

## Where this comes from

Weight 12 of 100 in Project & task management: 7 of 58 accounts; silent drops of due_at, dueDate and assignees, half of a 12-item monday update failing, bulk delete costing 20+ model passes, token-heavy grooming, and a Basecamp CLI archive that removed more than intended.

As data: https://www.anchorterminal.com/api/v1/use-cases/project-management.update-tasks.json, or the MCP tool get_use_case with id project-management.update-tasks. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
