# Pick up a ticket, act on it and update it

> 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 & productivity with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/productivity.work-issue/
- Markdown: https://www.anchorterminal.com/niches/productivity.work-issue/index.md (~1,050 tokens)
- Slim: https://www.anchorterminal.com/niches/productivity.work-issue/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/productivity.work-issue/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 | 3 | 6 | 30 | 9 |

## What counts as done

The 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.

Measured, for our own tests: at most two calls per issue, and bulk triage of 20 issues in under 10 calls.

How 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

## 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.

- **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.
- **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.
- **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.

- 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.
- 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.
- 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.
- 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.
- not this job: Zulip (Kandra Labs, Inc.): The API covers messages, channels, topics and users; there are no issues with statuses.

## What stops agents finishing

- a write reports success but drops the comment or attachment
- moving to a status needs a transition id from a tool that isn't loaded
- one-issue-per-call tools make triage cost a model turn per issue

## Around it

Before: productivity.find-context. After: code.open-pr, productivity.post-message.

## Where this comes from

Weight 30 of 100 in Work & 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

As 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.

---

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