{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/productivity.work-issue/",
    "json": "https://www.anchorterminal.com/niches/productivity.work-issue/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/productivity.work-issue/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/productivity.work-issue/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 | 3 | 6 | 30 | 9 |\n\n## What counts as done\n\nThe issue moved to the named status and a comment written, every reported change visible on re-read, attachments intact, and bulk triage of 20 issues.\n\nMeasured, for our own tests: at most two calls per issue, and bulk triage of 20 issues in under 10 calls.\n\nHow agents ask for it: work on PROJ-123; move this ticket to Done; comment on the issue with what you changed; triage the new bugs\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- **Atlassian Rovo MCP Server (Atlassian Pty Ltd)**: transitionJiraIssue and addOrEditJiraIssueComment exist, but moving to a named status takes three calls including listJiraIssueTransitions (acc-26), a comment passed with a transition is dropped while reporting success (acc-27), and with no bulk tools triage of 20 issues takes about 40 calls (acc-30). All open.\n- **Linear MCP (Linear Orbit, Inc.)**: The MCP updates issues and adds comments, and acc-09 found ticket management simple. Tools mirror the API one object per call (acc-11, 32 tools), and the GraphQL issueBatchUpdate isn't documented as an MCP tool, so 20-issue triage in under 10 calls is unproven.\n- **Notion MCP (Notion Labs, Inc.)**: A task database page can have its status property changed with notion-update-page and a comment added with the comments tools, so one ticket takes two calls. Notion is not an issue tracker, and no bulk update of 20 pages was found.\n\n- not this job: Mattermost (Mattermost, Inc.): The REST API is for chat: posts, channels, teams and users. It has no issue objects to transition or comment on.\n- not this job: Microsoft Teams (Microsoft Graph) (Microsoft Corporation): The Teams API covers teams, channels, chats and messages; it has no issue objects to transition.\n- not this job: Outline (General Outline, Inc.): Outline is a wiki; the API has documents, collections and comments but no issues or statuses to transition.\n- not this job: Slack MCP Server (official) (Slack Technologies, LLC (a Salesforce company)): The tools cover search, messages, canvases, users, files and lists; Slack has no issue objects with statuses to transition.\n- not this job: Zulip (Kandra Labs, Inc.): The API covers messages, channels, topics and users; there are no issues with statuses.\n\n## What stops agents finishing\n\n- a write reports success but drops the comment or attachment\n- moving to a status needs a transition id from a tool that isn't loaded\n- one-issue-per-call tools make triage cost a model turn per issue\n\n## Around it\n\nBefore: productivity.find-context. After: code.open-pr, productivity.post-message.\n\n## Where this comes from\n\nWeight 30 of 100 in Work \u0026 productivity: 9 of 36 accounts: Jira tickets driving coding agents (DNS change, requirements, cross-board tasks), Linear in the terminal, and the Atlassian MCP transition, bulk and attachment issues\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/productivity.work-issue.json, or the MCP tool get_use_case with id productivity.work-issue. 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": "Pick up a ticket, act on it and update it",
        "url": ""
      }
    ],
    "description": "Pick up a ticket, act on it and update it: 0 companies fully do it, 3 with a limit, 6 carry the tag. Every listing in Work \u0026 productivity with the reason and a source.",
    "facts": null,
    "h1": "Pick up a ticket, act on it and update it",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/productivity.work-issue/",
    "published": "",
    "section": "agents",
    "title": "Pick up a ticket, act on it and update it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/productivity.work-issue/"
  },
  "tokens": {
    "markdown": 1050,
    "slim": 230
  },
  "version": 1
}
