Niches · Work & productivity

Pick up a ticket, act on it and update it

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
3companies, fit with a limit
6companies carry the tag
30share of the category's work
9first-hand accounts

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. No docs we read state these figures, so they don't count against a listing here.

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 3

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.

ListingWhy
Atlassian Rovo MCP Server C
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. source
Linear MCP C
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. source
Notion MCP B
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. source

Doesn't do this job 5

Listings in the category that do something else, with the reason.

ListingWhy
Mattermost C
Mattermost, Inc.
The REST API is for chat: posts, channels, teams and users. It has no issue objects to transition or comment on. source
Microsoft Teams (Microsoft Graph) D
Microsoft Corporation
The Teams API covers teams, channels, chats and messages; it has no issue objects to transition. source
Outline D
General Outline, Inc.
Outline is a wiki; the API has documents, collections and comments but no issues or statuses to transition. source
Slack MCP Server (official) B
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. source
Zulip C
Kandra Labs, Inc.
The API covers messages, channels, topics and users; there are no issues with statuses. source

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

The same as data: /api/v1/use-cases/productivity.work-issue.json, or the MCP tool get_use_case with id productivity.work-issue. Other jobs in this category: /api/v1/niches?category=productivity.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.