{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/project-management.coding-agent-ticket-loop/",
    "json": "https://www.anchorterminal.com/niches/project-management.coding-agent-ticket-loop/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/project-management.coding-agent-ticket-loop/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/project-management.coding-agent-ticket-loop/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 | 17 | 20 | 21 | 12 |\n\n## What counts as done\n\nThe agent reads the ticket with its description, comments and attachments in one call, posts at least a plan comment and a completion comment, and changes status to the done state, with each write visible in the tracker's activity history.\n\nHow agents ask for it: pick up the next ticket assigned to you; work on PROJ-123; comment your plan on the issue before you start; move it to done and summarise what changed\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.)**: get_task returns comments by default, get_attachments gives download URLs, add_comment and update_tasks complete it, but attachments are a second call, about 44 tools load at once and MCP grants carry no scopes.\n- **Basecamp (37signals LLC)**: To-dos, comments and uploads are separate endpoints, so a ticket read takes several calls; completion and comment writes exist, and basecamp mcp --read-only and --domains narrow the tool set.\n- **ClickUp (Mango Technologies, Inc. DBA ClickUp)**: Get Task, Get Task Comments and Download Task Attachment read a ticket and attachments, comment and status writes exist, but that is three calls and 65 tools load with no profile or read-only grant.\n- **monday.com (monday.com Ltd.)**: get_updates, get_assets and create_update cover reading comments and files and posting, and status is a column write, but reads span several calls, 60+ tools load, and acc-25 found read-only mode left only ids and names.\n- **ONES (The Beautiful ONES Technology PTE. LTD.)**: get_issue_details, get_list_of_issue_comments, download_attachment, post_issue_comment and execute_issue_workflow cover the loop and scopes can be narrowed per category, but the read is three calls and 60+ tools load at once.\n- **OpenProject (OpenProject GmbH)**: MCP reads a work package and its comments, posts comments and updates status, but no MCP tool reads attachments (APIv3 does), and the server is an Enterprise add-on, which pushed acc-54 to build its own.\n- **Plane (Plane Software, Inc.)**: retrieve_by_identifier takes ENG-42, attachment read returns images and text inline, and comments and state updates are actions, but comments and attachments are separate calls; acc-16 runs this loop with AGENTS.md rules.\n- **Redmine (Redmine project)**: GET /issues/\u003cid\u003e?include=attachments,journals returns description, comments and attachments in one call, and a PUT with notes and status_id comments and closes it, but the key carries its user's full permissions and there is no MCP server.\n- **Roma (Milo Mode Inc.)**: Items can be delegated to a registered agent, get_item with includeFiles returns attached file text and image URLs, and post_chat_message posts on the item's thread, but every token reaches the whole workspace with no read-only grant, and 42 tools load.\n- **Shortcut (Shortcut Software Company)**: The MCP has full story support including comments, and scopes split read, story-write and comment-write, but acc-34 found the MCP can upload files and not download them, so screenshots on a ticket can't be read.\n- **Taiga (Taiga Cloud Services, S.L.)**: Issues and user stories have get, comment-by-edit, attachment list and status endpoints over REST, but reading description, comments (history) and attachments takes three calls, and the token is a 24-hour login with the account's full permissions.\n- **Taskade (Taskcade Inc.)**: read_project returns the task tree with assignees and dates and complete_task closes a task, but no MCP tool reads or posts task comments and attachments aren't readable per task; the hosted server also needs a paid plan.\n- **Teamwork.com (Teamwork Crew Limited)**: Task get, comment list and create, file get and download_file and complete_task cover the loop, and profile endpoints narrow tools, but comments and files are separate calls and acc-51 saw an EU site fail to connect from Codex.\n- **Todoist (Todoist Inc.)**: fetch-object, find-comments, view-attachment, add-comments and complete-tasks cover the loop, but the read is several calls, 47 tools load at a fixed cost near 35,700 tokens, and the hosted server grants read and write only.\n- **Trello (Trello, Inc.)**: A card read can include attachments and comment actions, attachment and comment endpoints exist, and moving a card to a Done list is a field change, but no official MCP server exists and an unattended agent relies on the key and token, which can be read-scoped.\n- **Wrike (Wrike, Inc.)**: get_item_details returns status, assignees and attachments, get_item_comments reads up to 200 comments, and create_item_comment and update_items write back, but that is two reads, attachments come as metadata and links, and acc-52 saw OAuth token exchange fail in Claude Code.\n- **YouTrack (JetBrains s.r.o.)**: get_issue, get_issue_comments, add_issue_comment and update_issue cover the loop with a URL returned, and ?tools= narrows 23 tools, but no MCP tool reads attachments, and acc-53 saw goose fail to initialise against YouTrack 2026.2.\n\n- not this job: Financial Cents MCP (Financial Cents LLC): Financial Cents tracks accounting-firm work; manage_project_task has no comment field and no task comment tool appears, so a coding agent cannot post plan and completion comments on a ticket.\n\n## What stops agents finishing\n\n- MCP server loads dozens of tools and fills the coding agent's context\n- attachments can be uploaded but not read back\n- no credential that limits a headless agent to its own tickets\n- OAuth connect fails in the coding client (redirect URI rejected, no dynamic client registration)\n\n## Around it\n\nBefore: project-management.find-work. After: code.open-pull-request, messaging.post-update.\n\n## Where this comes from\n\nWeight 21 of 100 in Project \u0026 task management: 12 of 58 accounts; HN commenters running Jira, Linear, Plane, Redmine, Asana and monday boards as the queue for Claude Code or Codex, plus four who dropped tracker MCPs for a markdown file, a CLI or their own board because of token cost or broken servers. Four accounts are on Jira and Linear, which are not listed; they show the job, not a listing.\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/project-management.coding-agent-ticket-loop.json, or the MCP tool get_use_case with id project-management.coding-agent-ticket-loop. 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": "Coding agent picks up a ticket, works it and reports back on the ticket",
        "url": ""
      }
    ],
    "description": "Coding agent picks up a ticket, works it and reports back on the ticket: 0 companies fully do it, 17 with a limit, 20 carry the tag. Every listing in Project \u0026 task management with the reason and a source.",
    "facts": null,
    "h1": "Coding agent picks up a ticket, works it and reports back on the ticket",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/project-management.coding-agent-ticket-loop/",
    "published": "",
    "section": "agents",
    "title": "Coding agent picks up a ticket, works it and reports back on the…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/project-management.coding-agent-ticket-loop/"
  },
  "tokens": {
    "markdown": 1850,
    "slim": 380
  },
  "version": 1
}
