{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/project-management.update-tasks/",
    "json": "https://www.anchorterminal.com/niches/project-management.update-tasks/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/project-management.update-tasks/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/project-management.update-tasks/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 18 | 20 | 12 | 7 |\n\n## What counts as done\n\nEvery 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.\n\nHow 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\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **Basecamp (37signals LLC)**: PUT /todos/\u003cid\u003e.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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **OpenProject (OpenProject GmbH)**: update_work_package changes one work package in place a call with lockVersion conflicts returning 409; no bulk update tool.\n- **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.\n- **Redmine (Redmine project)**: PUT /issues/\u003cid\u003e changes one issue a call; no bulk endpoint, and errors other than validation failures return a status with no body.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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).\n\n## What stops agents finishing\n\n- update returns success while dropping the field\n- no batch endpoint, so 50 changes cost 50 model turns\n- archive or delete semantics differ from the web app, so humans cannot find what the agent removed\n\n## Around it\n\nBefore: project-management.find-work. After: project-management.status-report, messaging.post-update.\n\n## Where this comes from\n\nWeight 12 of 100 in Project \u0026 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.\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Change many tasks at once: reschedule, reassign, rename, close or groom",
        "url": ""
      }
    ],
    "description": "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 \u0026 task management with the reason and a source.",
    "facts": null,
    "h1": "Change many tasks at once: reschedule, reassign, rename, close or groom",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/project-management.update-tasks/",
    "published": "",
    "section": "agents",
    "title": "Change many tasks at once: reschedule, reassign, rename, close or…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/project-management.update-tasks/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 380
  },
  "version": 1
}
