Niches · Project & task management
Change many tasks at once: reschedule, reassign, rename, close or groom
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
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 18
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.
| Listing | Why |
|---|---|
| Asana BB 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. source |
| Basecamp B 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. source |
| ClickUp B 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. source |
| Financial Cents MCP E 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. source |
| monday.com BB 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. source |
| ONES D 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. source |
| OpenProject D OpenProject GmbH | update_work_package changes one work package in place a call with lockVersion conflicts returning 409; no bulk update tool. source |
| Plane B 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. source |
| Redmine E 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. source |
| Roma D 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. source |
| Shortcut B 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. source |
| Taiga F 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. source |
| Taskade C 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. source |
| Teamwork.com B 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. source |
| Todoist B 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. source |
| Trello B Trello, Inc. | PUT /cards/{id} changes one card a call; /batch takes up to 10 GET requests only, so 50 changes are 50 calls. source |
| Wrike C 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. source |
| YouTrack F 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). source |
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.
The same as data: /api/v1/use-cases/project-management.update-tasks.json, or the MCP tool get_use_case with id project-management.update-tasks. Other jobs in this category: /api/v1/niches?category=project-management.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.