LoginSign Up
← Back to PM
Weekly · PM · Week of May 25, 2026

Jira, Linear, Aha! and Avaza all ship agent endpoints in one week — the project tracker becomes an agent surface.

mcpagent-orchestrationenterprise-governancerules-enginerbacopinionated-automation
O
By Onur Öztürk
LinkedIn ↗
Generated 1h agoDrawn from 11 products

The week in project management

The dominant pattern this week is the work tracker becoming an addressable surface for external AI agents rather than a destination for human users. Atlassian shipped Cursor as an assignable agent inside Jira on May 20, four days after adding Claude Code to Agentic Pipelines, and the launch copy explicitly reframes Jira as 'your agent orchestration platform.' Linear closed the same week by auto-spinning a Slack channel per project and seating Linear Agent inside it. Aha! shipped a Model Context Protocol server exposing roadmaps, records, and reports to Claude, ChatGPT, and Copilot. Avaza, the smallest vendor in this group by an order of magnitude, shipped its own MCP server a few weeks earlier. Four products at four different price points, all making the same bet: the place AI calls into.

The countervailing pattern is just as legible. Asana and Plane spent the week shipping permissions infrastructure — RBAC View into release preview, Teamless Projects, custom roles, per-resource overrides — the unglamorous prerequisites for selling agentic capability to enterprises that still need to know which contractor saw which task. MeisterTask gated a new workload planner to Enterprise; SmartSuite stacked multi-page forms, Internal forms, and two-way Microsoft Teams actions into an ITSM/GRC pitch. The two arcs are not in tension. They are the same arc: vendors are simultaneously opening the platform to outside agents and hardening the governance layer that makes opening it a defensible enterprise sale.

Leaders

  • Linear — Code Intelligence (May 14) lets Linear Agent read the codebase through GitHub with per-repo admin allowlists; Project Slack channels (May 21) auto-create a channel per project and add an Asks Agent that triages free-form Slack requests into structured issues. Three sparks in seven days, all reinforcing the thesis that Linear Agent is becoming the product's primary surface rather than a feature inside it.
  • Atlassian — Cursor in Jira (May 20) and Claude Code on Agentic Pipelines (May 19) confirm Atlassian is treating Jira as the neutral assignment layer over competing coding agents, not the host of its own. Rovo Dev CLI's new Research Mode lands in the same week as a defensive move — first-party agent gets sharper context-gathering as third-party agents become assignable.
  • Asana — Scheduled Triggers V2 (May 18) introduces an 'execution scope' primitive that lets time-driven rules act on existing tasks, explicitly flagged as step one of a broader Rules engine rearchitecture. RBAC View Permissions hit Release Preview for Enterprise+ with June 2 GA, and Teamless Projects relaxes the oldest structural constraint in the product. Two-track week: rules engine and governance, both backlog-clearing.
  • Plane — May 15 lands PQL — a custom query language — as the way Dashboards are built, and Plane AI moves from suggesting to editing pages. Stacked on April 25's permissions redesign (two-layer access model, custom roles for Enterprise), this is a coordinated move up-market against Linear and Jira at the enterprise tier.
  • Aha! — The Aha! software MCP server (May 20) exposes records, reports, and plans to external agents, while Aha! Builder gains in-prototype feedback widgets (May 18) and prototype-as-record linkage (May 13). Aha! is repositioning from roadmap tool to AI-native surface where product work starts.

Wildcards

  • Avaza — An SMB professional-services vendor shipping an MCP server (May 1) is the off-pattern move of the week. The same release window includes a complete subtasks rebuild and customizable project statuses — Avaza is closing parity gaps against Asana and ClickUp while simultaneously betting on being the system AI agents read billable hours and invoices out of.
  • Sunsama — Task Priority and Auto-Sort graduated from beta on May 6, with Sunny gaining persistent memory and an MCP gettaskby_id tool in adjacent drops. Sunsama, historically the manual-planner holdout, is now willing to reorder a user's day automatically — a philosophical shift, not a feature add.
  • HoneyBook — First major geographic expansion in years: UK and Australia launched simultaneously on May 21. Off-pattern because nothing else in the sector moved on geography this week; on-pattern because the comparison content underneath (vs. ClickUp, vs. Bloom) signals horizontal PM tools are eating into HoneyBook's client-management niche and international TAM is the response.

Themes that compounded

  • MCP servers as a vendor primitive — Linear, Atlassian (via Agentic Pipelines), Aha!, and Avaza all shipped or extended MCP surfaces in the same window, spanning enterprise PM through SMB services.
  • Enterprise governance arriving alongside AI — Asana's RBAC and Teamless Projects, Plane's custom roles and per-resource overrides, and MeisterTask's plan-gated workload planner all landed in parallel with agent moves elsewhere.
  • Opinionated automation replacing manual coordination — Asana's Scheduled Triggers V2 reaching into existing project state, Sunsama's Auto-Sort reordering the day, SmartSuite's Loop Over Field Values and two-way Teams actions all push work from human-driven to rule-driven.
  • The agent as orchestration layer, not assistant — Atlassian's explicit 'agent orchestration platform' framing for Jira, Linear Agent's Slack ingress, and Aha!'s MCP positioning all treat the AI as a routing target, not a chat widget.

Watch this week

The next signal to watch is whether the MCP wave produces write-action depth or stalls at read access. Linear Agent already has codebase-read plus MCP allowlists; Aha! and Avaza have shipped MCP surfaces but the public framing emphasizes read more than mutation. The vendor who first lets external agents reliably create, edit, and route work items through MCP without breaking permissions will define the next quarter's reference architecture. On the governance side, Asana's RBAC GA is scheduled for June 2 and Plane's custom-roles redesign telegraphs SCIM and audit logs as the next checkboxes — both worth watching as proof points that the enterprise-PM market is becoming a two-front war between agent surface area and access control.