Linear vs Jira
free-tier · subscription-per-seat · enterprise-custom · credits
·free-tier · subscription-per-seat · enterprise-custom
Linear wins · 39–14 (22 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to LinearLinear's developer docs are exposed as clean .md pages (agents.md, graphql.md, webhooks.md, sdk.md, aig.md), a pattern consistent with agent-oriented/llms.txt-style documentation that an AI agent could be pointed at directly. However, there's no explicit llms.txt file cited, no first-party statement framing these docs as agent-consumption-optimized, and no independent evidence of an agent successfully using them this way. Missing for 10: explicit llms.txt manifest, documentation of agent-readability intent, third-party confirmation of successful agent consumption.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “The agent must signal its identity clearly so that it can never be mistaken for a person.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to LinearLinear exposes a full GraphQL API with API-key and OAuth2 authentication, a typed SDK, webhooks for event-driven automation, and documented rate limits/deprecation policy — all of which allow scripting issue creation, queries, and workflow automation entirely headlessly (e.g. from CI pipelines) without the UI. Missing for 10: no dedicated CLI tool or explicit CI/GitHub Actions integration guide, and no independent hands-on report of using the API in a CI pipeline.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
Jira exposes a REST API and JQL that community members report using for scripted/automated interactions (e.g., writing API wrapper scripts, running REST queries), suggesting headless automation is possible, but there is no first-party documentation of CI-specific workflows, official CLI, or automation pipeline examples, and probes for OpenAPI/llms.txt discovery failed. missing for 10: explicit CI/headless automation docs, official CLI or SDK for pipelines, discoverable API spec (OpenAPI 404s).
- [claimed-docs] “Rich APIs”
- [community] “Due to the slow loading, I ended up writing some simple Jira API wrapper scripts for submitting bug reports quicker in our systems.”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Does Plane offer an alternative for JQL (Jira Query Language)? That's what I appreciate most about Jira.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.atlassian.com/openapi.json, https://developer.atlassian.com/swagger.json, https://…”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnLinearnone0/10All MCP-related evidence (linear-probe-1, linear-docs-67, linear-intdir-4, linear-intdir-6) describes Linear exposing its OWN MCP server so that other tools (Cursor, Claude) can connect TO Linear — the opposite direction from the story, which asks whether a user can plug external MCP servers INTO Linear so Linear's agent can use their tools. No evidence shows Linear or Linear Agent consuming/importing third-party MCP servers as a client.
- [probe] “official MCP server documented at https://linear.app/docs/mcp”
- [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
- [claimed-docs] “Connect Cursor to the Linear MCP server”
- [claimed-docs] “Connect Claude to the Linear MCP server”
Jiranone0/10The evidence pack only shows Jira/Atlassian exposing an official MCP server (jira-probe-3), which is the reverse capability (Jira's tools being consumed by other agents), not Jira itself acting as an MCP client that plugs in external MCP servers to use their tools. No documentation of Rovo AI or any Jira feature connecting to third-party MCP servers is present.
- [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnLinear publishes an official MCP server (docs page at linear.app/docs/mcp) and the changelog confirms ongoing feature work on it (e.g., Okta-based access management via Linear's MCP), showing agents can connect through this official channel. Missing for 10: independent/hands-on verification of the MCP server in use and detailed docs on setup/tool coverage beyond the single probe reference.
- [probe] “official MCP server documented at https://linear.app/docs/mcp”
- [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
There's evidence of an official Atlassian MCP server repo (jira-probe-3) enabling agent connections, but the evidence pack lacks deeper documentation on setup, capabilities, or independent hands-on validation. Missing for 10: detailed first-party docs on the MCP server's features/auth, and independent corroboration of it working in practice.
- [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
ai-native userUse an official CLI
weight 2 · round drawnLinearnone0/10The evidence pack documents Linear's GraphQL API, TypeScript SDK, webhooks, OAuth, and MCP server, but nowhere mentions an official command-line interface (CLI) tool for interacting with Linear. Since CLI is a plausible and common tool for developer-facing products, its absence here is a gap rather than an inapplicable axis.
Jiranone0/10No evidence of an official Jira CLI anywhere in the pack; evidence covers APIs, integrations, MCP server, and community feedback but nothing about a first-party command-line interface. missing for 10: any mention of an official Jira CLI tool, its docs, install method, or command reference.
ai-native userDrive the product through a documented public API
weight 3 · round to LinearLinear ships a well-documented public GraphQL API with introspection, an explorable schema via Apollo Studio, OAuth2/API-key auth, TypeScript SDK, webhooks, rate-limit documentation, and a deprecation policy, giving AI-native users a robust way to programmatically drive the product. missing for 10: independent hands-on developer reports validating real-world API usage/reliability beyond Linear's own docs.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
- [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
Jira advertises 'Rich APIs' and community members independently confirm and actively use a REST API (writing wrapper scripts, running JQL queries) to drive Jira programmatically, showing real-world API access beyond marketing claims. Missing for 10: a first-party OpenAPI/swagger spec or llms.txt discovery (probes returned 404s at guessed paths) and direct citation of official API reference docs.
- [claimed-docs] “Rich APIs”
- [community] “Due to the slow loading, I ended up writing some simple Jira API wrapper scripts for submitting bug reports quicker in our systems.”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Does Plane offer an alternative for JQL (Jira Query Language)? That's what I appreciate most about Jira.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developer.atlassian.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.atlassian.com/openapi.json, https://developer.atlassian.com/swagger.json, https://…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to LinearLinear documents OAuth2 apps with distinct scopes (e.g. app:assignable, app:mentionable) for building agents, admin approval workflows for third-party apps, and per-key rate limits differentiated by auth type, which together enable a degree of least-privilege credentialing for agent integrations. However, personal API keys (the simpler credential path) are not shown to be scope-limited, and there's no first-party or independent evidence of fine-grained per-resource/action scoping akin to full least-privilege IAM. Missing for 10: documentation of scoped personal API keys, granular resource-level permission control beyond the small named scope list, and independent/hands-on verification of least-privilege enforcement.
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
- [claimed-docs] “app:assignable | Allow the app to be assigned as a delegate on issues and made a member of projects app:mentionable | Allow the app to be me…”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
- [claimed-docs] “Use URL parameters to send users directly to a pre-filled Create OAuth App form in Linear. An equivalent JSON manifest format lets you store…”
- [claimed-docs] “Admins can manage access centrally, without requiring employees to sign in or authorize Linear individually.”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
Jiranone0/10The evidence pack only mentions 'Rich APIs' and SSO/SAML generically, with no documentation of scoped or least-privilege API tokens, OAuth scopes, or agent-specific credential issuance. No first-party or community evidence describes granular permission scoping for API/agent access.
ai-native userBuild against official SDKs
weight 2 · round to LinearLinear publishes an official TypeScript SDK exposing its GraphQL schema with strongly typed models (linear-docs-53, linear-docs-89, linear-docs-93), backed by full GraphQL API docs, introspection, published schema SDL, OAuth2/API key auth, rate limits, and deprecation policy (linear-supp-graphql-introspection, linear-supp-apollo-explorer, linear-supp-rate-limits, linear-supp-deprecations, linear-docs-99, linear-docs-50). This gives AI-native developers a solid, well-documented official SDK to build against. Missing for 10: independent/hands-on developer corroboration (e.g., GitHub stars, community usage reports) of the SDK itself beyond official docs, and SDKs in languages beyond TypeScript.
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “Install the Linear SDK to use strongly typed models and operations”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
Evidence shows Jira exposes a REST API that developers (including community members) use to build scripts and integrations, and 'Rich APIs' is claimed on the marketing page, but there is no evidence of an official language SDK (Python/JS/Java client libraries) or published API spec — probes for openapi/llms.txt both 404. Missing for 10: dedicated SDK documentation/repos, published OpenAPI spec, and first-party language client libraries.
- [claimed-docs] “Rich APIs”
- [community] “Due to the slow loading, I ended up writing some simple Jira API wrapper scripts for submitting bug reports quicker in our systems.”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developer.atlassian.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.atlassian.com/openapi.json, https://developer.atlassian.com/swagger.json, https://…”
ai-native userSubscribe to events via webhooks
weight 2 · round to LinearLinear provides documented webhooks with a webhookCreate mutation to subscribe to HTTP push notifications for data create/update/delete events, plus in-app event subscriptions for project views routed to Inbox/Slack, giving AI-native users clear ways to consume event streams programmatically. Missing for 10: independent/hands-on corroboration of webhook reliability or payload completeness beyond first-party docs.
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
ai-native userHand off work between tools or agents without losing context or information
weight 1 · round to LinearLinear documents extensive hand-off machinery for agentic work: issues can be delegated (not assigned) to AI agents while humans retain ownership, agents behave like workspace members (mentions, comments, docs) so context stays attached to the issue, and MCP/integration connectors (GitHub, Copilot, Codex, Claude, Cursor, Slack) let work flow between tools while Linear remains the shared context hub. Features like 'Write with Agent' (pulls prior updates plus Slack context), checkpoints/version history, guided reviews with before/after screenshots, and Loops updating linked docs/Slack on changes all reinforce continuity across handoffs. missing for 10: independent/hands-on verification that context genuinely survives cross-tool handoffs (all evidence is first-party docs), and no explicit benchmark/comparison of information loss vs other tools
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Assigning an issue to your app now sets it as the delegate, not the assignee—so humans maintain ownership while agents act on their behalf.”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
- [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
- [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation. It also captures before-and-after screenshots”
- [claimed-docs] “Linear Agent can now write code using Claude Code and Codex.”
- [claimed-docs] “Connect Cursor to the Linear MCP server”
- [claimed-docs] “Connect Claude to the Linear MCP server”
- [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
Jira offers rich APIs, 3000+ Marketplace integrations, and cross-tool tracking (Slack, Figma, Gmail) plus a documented official MCP server enabling agent connectivity, which supports moving work/context across tools. However, there's no direct evidence describing context preservation specifically during agent-to-agent or tool-to-tool handoffs, and community reports note data-loss and UI issues (e.g., saving errors, ticket reassignment confusion) that raise doubts about seamless continuity. Missing for 10: explicit documentation of context/state preservation across handoffs, independent verification of the MCP server's agentic handoff behavior, and case studies of multi-tool agent workflows.
- [claimed-docs] “Keep work up-to-date by tracking progress from your favorite tools like Slack, Figma and Gmail powered by an AI-assist”
- [claimed-docs] “Choose from the over 3000+ integrations available in the Atlassian Marketplace.”
- [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
- [community] “I routinely lose data in jira, like saving errors. Dragging and dropping attachments sometimes causes the page to crash and reload. Everythi…”
- [community] “As a developer, once I finish my ticket I assign it to a QA. Then I can never get back to the ticket... completed tickets aren't assigned to…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to LinearLinear ships AI-agent features (Write with Agent for project updates, Loops for automated doc/plan updates, auto-triage/routing of feedback into issues, Linear Agent investigating issues) that surface generated content and suggestions inside the product, per linear-docs-19, linear-docs-38, linear-docs-45, linear-docs-62, linear-docs-95-97. However, these are framed as agentic task-execution/automation rather than analytic 'insights' (e.g., trend analysis, prioritization recommendations, summarization dashboards), and there's no independent/hands-on evidence validating quality of these AI outputs. missing for 10: dedicated insight/analytics generation (e.g., pattern detection across issues, predictive suggestions, summarized health reports) and third-party corroboration of suggestion quality.
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
- [claimed-docs] “Automatically turn conversations and customer feedback into actionable issues that are instantly routed, labeled, and prioritized for the ri…”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
Atlassian's own docs describe Rovo AI generating insights (trend identification, bottleneck detection) and suggestions (breaking big ideas into tasks, automated status reminders) directly from Jira data, matching the story's intent. However, all evidence is vendor marketing copy with no independent/hands-on validation of these AI features' actual quality or reliability, and community discussion never mentions Rovo AI at all. Missing for 10: independent or hands-on evaluation of Rovo AI insight accuracy/usefulness, and community corroboration of the AI features themselves.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
- [claimed-docs] “Use Rovo AI to identify trends to surface new opportunities and remove bottle necks.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to LinearLinear's "Loops" feature explicitly lets users describe a job in plain language and set it to run on a schedule or in response to events, enabling autonomous background automations (e.g., updating docs, posting Slack updates, monitoring initiatives) without manual triggering. This is well documented across multiple changelog entries describing scheduling, event triggers, and recurring workflows. Missing for 10: independent/hands-on verification of reliability at scale and no third-party community confirmation of autonomous background execution in practice.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “You can now add a loop to Favorites”
Jira has documented automation rules and Rovo AI features (auto-reminders, rules that move work forward, auto-assignment) that can run in the background without manual triggering, per jira-docs-4 and jira-docs-10. However, evidence is purely first-party marketing copy with no hands-on validation of autonomy, reliability, or how 'agentic' these automations truly are, and community feedback focuses on unrelated UI/performance complaints rather than confirming automation robustness. Missing for 10: independent/hands-on verification of autonomous automation execution, technical documentation of automation rule engine capabilities/limits, and evidence of complex multi-step autonomous workflows beyond simple reminders.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
- [claimed-docs] “Use Rovo AI to identify trends to surface new opportunities and remove bottle necks.”
- [claimed-docs] “Rovo AI connects relevant assets and rich data from Confluence, Figma, and your 3rd party apps to your work.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to LinearLinear ships a built-in 'Linear Agent' that users can delegate issues to directly (assign/mention), which writes code via Claude Code/Codex, edits text, runs Loops for recurring work, drafts project updates, and shows delegated work status in My Issues, all documented extensively in first-party changelog docs. missing for 10: independent/hands-on verification beyond vendor changelog, and clearer detail on reliability/limits of the built-in assistant in real-world use.
- [claimed-docs] “Linear Agent can now write code using Claude Code and Codex.”
- [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
- [claimed-docs] “We’ve also added section under My Issues → Assigned for your delegated issues. It shows the status of each coding session, and gives you a q…”
- [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “You can now edit text with Linear Agent, and use Loops to keep docs and project descriptions up-to-date.”
- [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
- [claimed-docs] “@Linear can you take a stab at this?”
Atlassian's own docs describe Rovo AI as a built-in assistant that can break down tasks, auto-assign them, run automations, and surface trends — matching the 'delegate tasks to an AI assistant' story. However, all evidence is vendor marketing copy with no independent/hands-on confirmation that Rovo actually executes delegated tasks reliably. Missing for 10: independent or hands-on validation of Rovo AI task delegation, detail on scope/limits of what it can autonomously do, and community feedback on its real-world reliability.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
- [claimed-docs] “Use Rovo AI to identify trends to surface new opportunities and remove bottle necks.”
ai-native userOperate the product with natural-language commands
weight 2 · round to LinearLinear supports natural-language interaction extensively: users can @mention Linear Agent, describe jobs in plain language for Loops, use 'Write with Agent' to draft updates, and delegate issues via comments in natural language (linear-docs-11, -19, -36, -41, -68). This is well documented across multiple first-party changelog entries and the agents.md docs, but missing for 10: independent/hands-on evidence of natural-language command accuracy or limitations, and no dedicated NL command palette/chat interface separate from agent-delegation workflows.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
- [claimed-docs] “@Linear can you take a stab at this?”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
Jira's Rovo AI features (task breakdown, automations, trend surfacing) imply some natural-language assistance, and an official Atlassian MCP server exists that would let AI agents translate natural-language requests into Jira actions, but there is no direct documentation or hands-on evidence of a chat-style natural-language command interface within Jira itself. Missing for 10: first-party docs demonstrating actual NL command execution in-product, independent/hands-on confirmation that Rovo AI or MCP-driven commands reliably operate Jira.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
- [claimed-docs] “Use Rovo AI to identify trends to surface new opportunities and remove bottle necks.”
- [claimed-docs] “Rovo AI connects relevant assets and rich data from Confluence, Figma, and your 3rd party apps to your work.”
- [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
ai-native userBuild and configure my own custom AI agent within the product
weight 2 · round to LinearLinear offers in-product mechanisms for creating custom agent-like automation: Loops let users 'describe the job in plain language' and set it to run on a schedule or event (linear-docs-36/95-100), and Skills let teams codify and share recurring agent workflows (linear-docs-23/46). Linear also documents a developer-facing Agents API for building agents that behave like workspace members (assignable, mentionable, can comment) (linear-docs-16, linear-docs-54/64/75/90/94). This is meaningful but falls short of a full custom-agent builder with model/tool selection or a dedicated no-code agent studio. Missing for 10: no evidence of choosing/configuring underlying models or custom toolsets, no dedicated 'agent builder' UI beyond Loops/Skills, and no independent hands-on confirmation of ease-of-use.
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
- [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
- [claimed-docs] “Build agents that can investigate incidents, monitor SLAs, or analyze customer feedback.”
- [claimed-docs] “How to best integrate an AI agent into Linear”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “app:assignable | Allow the app to be assigned as a delegate on issues and made a member of projects app:mentionable | Allow the app to be me…”
Jiranone0/10Evidence shows Rovo AI features (automations, task breakdown, trend surfacing) but no documentation of a builder/studio where users can create and configure their own custom AI agents within Jira. Missing for 10: any mention of an agent-builder/agent-configuration interface, examples of custom agent creation, or docs on agent permissions/tools.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
- [claimed-docs] “Use Rovo AI to identify trends to surface new opportunities and remove bottle necks.”
- [claimed-docs] “Rovo AI connects relevant assets and rich data from Confluence, Figma, and your 3rd party apps to your work.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to LinearLinear's GraphQL API supports introspection and is explorable/queryable via Apollo Studio Explorer with no login required, effectively an interactive reference with runnable queries, plus published docs with sample queries/mutations and an SDK. However, this is a third-party hosted explorer rather than a first-party embedded interactive API reference, and there's no evidence of runnable examples directly within Linear's own developer docs site. missing for 10: first-party embedded interactive API console with runnable examples on developers.linear.app itself, independent/hands-on confirmation of the Apollo Explorer experience, broader runnable example coverage beyond basic query/mutation snippets.
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
- [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Learn how to use the GraphQL API to query and mutate your data”
Jiranone0/10No evidence of an interactive API reference or runnable-example console; probes explicitly show llms.txt and OpenAPI spec endpoints returning 404, and community mentions only note using the REST API and JQL, not an interactive documentation experience.
- [probe] “PROBE llms.txt: HTTP 404 at https://developer.atlassian.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.atlassian.com/openapi.json, https://developer.atlassian.com/swagger.json, https://…”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Does Plane offer an alternative for JQL (Jira Query Language)? That's what I appreciate most about Jira.”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to LinearLinear's API is GraphQL, not OpenAPI/REST, but it explicitly supports schema introspection and publishes a full schema SDL file in the linear/linear GitHub repo, plus an explorable schema via Apollo Studio — giving AI-native users machine-readable access to the API's shape without needing a human-written spec. This satisfies the intent of a downloadable machine-readable spec via GraphQL introspection/SDL rather than OpenAPI itself. missing for 10: no explicit OpenAPI/Swagger document, no single-click 'download spec' artifact, and no independent/community confirmation of using the introspection or SDL file in practice.
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Linear's public API is built using GraphQL.”
Jiranone0/10No evidence of a downloadable OpenAPI/Swagger spec exists; probes explicitly found 404s for openapi.json, swagger.json, and llms.txt at developer.atlassian.com, and community mentions only using the REST API/JQL, not a machine-readable spec file.
- [probe] “PROBE llms.txt: HTTP 404 at https://developer.atlassian.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.atlassian.com/openapi.json, https://developer.atlassian.com/swagger.json, https://…”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Due to the slow loading, I ended up writing some simple Jira API wrapper scripts for submitting bug reports quicker in our systems.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to LinearLinear's own docs explicitly state its GraphQL API 'doesn't have versioning like many REST APIs,' but they do document a deprecation policy: use of the @deprecated schema directive, proactive outreach for breaking changes, and changelog entries tagged [API]. This satisfies the 'documented deprecation policy' half of the story but directly contradicts the 'versioned APIs' half. Missing for 10: an actual versioning scheme (e.g., v1/v2 endpoints or dated API versions), and independent/community corroboration that deprecation notices are reliably honored in practice.
- [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
Jiranone0/10While Jira has a REST API referenced by community users (jira-comm-16, jira-comm-11), the evidence pack contains no documentation of API versioning practices or a deprecation policy, and probes for OpenAPI specs and llms.txt both returned 404s. Missing for 10: any first-party documentation of API version numbers, deprecation timelines, or migration guides for breaking changes.
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Due to the slow loading, I ended up writing some simple Jira API wrapper scripts for submitting bug reports quicker in our systems.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developer.atlassian.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.atlassian.com/openapi.json, https://developer.atlassian.com/swagger.json, https://…”
ai-native userThe documented API rate limits and concurrency caps before building automation at scale
weight 2 · round to LinearLinear's developer docs explicitly publish per-auth-type rate limits (API key, OAuth, unauthenticated), leaky-bucket refill behavior, complexity limits, and rate-limit response headers, giving AI-native builders concrete numbers to design automation around. Missing for 10: explicit documented concurrency caps (max simultaneous requests/connections) beyond hourly request quotas, and no independent/hands-on confirmation that these limits hold in practice at scale.
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
Jiranone0/10No evidence pack item documents specific API rate limits, throttling thresholds, or concurrency caps for Jira's REST/API platform; probes for OpenAPI/llms.txt specs both 404'd, and community mentions only reference general API/JQL usage, not documented limits. missing for 10: documented rate-limit numbers or headers, concurrency cap documentation, any first-party developer.atlassian.com rate-limit policy page.
- [probe] “PROBE llms.txt: HTTP 404 at https://developer.atlassian.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.atlassian.com/openapi.json, https://developer.atlassian.com/swagger.json, https://…”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Due to the slow loading, I ended up writing some simple Jira API wrapper scripts for submitting bug reports quicker in our systems.”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to JiraLinear's GraphQL API, SDK, and webhook system (linear-docs-49,53,51) provide the technical means to script bulk changes across issues, and there's a documented bulk import capability (linear-docs-47). However, there is no explicit documentation of a dedicated bulk-edit UI, batch mutation endpoints, or AI-agent-driven bulk operation workflow across many items at once. missing for 10: explicit bulk-edit/multi-select UI docs, batch/bulk GraphQL mutations, and any agent or automation example operating on multiple items simultaneously.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “Import data from other services into Linear”
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
Jira's REST API and JQL query language (cited by multiple community members) enable scripted bulk operations across issues, and users report writing wrapper scripts against the API for faster bulk actions. However, there is no first-party documentation specifically describing a native bulk-edit/bulk-operations feature or AI-native bulk automation workflow, and the OpenAPI/llms.txt discovery probes failed. Missing for 10: explicit bulk-operations UI/API documentation, AI-agent-oriented bulk automation examples, independent confirmation of scale/performance for bulk actions.
- [claimed-docs] “Rich APIs”
- [community] “Due to the slow loading, I ended up writing some simple Jira API wrapper scripts for submitting bug reports quicker in our systems.”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Does Plane offer an alternative for JQL (Jira Query Language)? That's what I appreciate most about Jira.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.atlassian.com/openapi.json, https://developer.atlassian.com/swagger.json, https://…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to LinearLinear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event (e.g., initiative/project/cycle changes), with concrete examples like auto-updating docs or posting Slack messages when a target date changes. This is reinforced by webhook support for event-driven automation via the API. Missing for 10: independent/hands-on corroboration beyond vendor docs, and detail on the breadth of definable trigger conditions/rules.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
Jira's docs explicitly describe an automation engine that lets users 'connect tools to any Jira workflow with automation' and 'create custom automations... from automated reminders to rules that move work forward' via Rovo AI, matching the rule/trigger/action pattern the story describes. However, the evidence is marketing-level with no deep technical documentation of the rule builder (triggers/conditions/actions) or independent hands-on validation of automation reliability. Missing for 10: detailed technical docs on the automation rule engine's trigger/condition/action model, and independent/community corroboration that automation rules work as advertised.
- [claimed-docs] “Connect your tools to any Jira workflow with automation. Whether your team is using Bitbucket, Slack, or any other tool, automation keeps Ji…”
- [claimed-docs] “Connect your tools to any Jira workflow with automation.”
- [claimed-docs] “Scale processes and save time with customizable workflows that integrate with your tech stack.”
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to LinearLinear's 'Loops' feature is explicitly designed for recurring agent workflows: users describe a job and choose to run it 'on a schedule or in response to an event,' with examples like auto-updating launch plans and posting Slack updates when project dates change. Docs also show loops can be shared as team-wide skills and pinned/favorited for ongoing use, covering both scheduling and workflow automation depth. Missing for 10: independent/hands-on confirmation that scheduled loops reliably trigger as configured, and technical detail on scheduling granularity or failure handling.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
- [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
- [claimed-docs] “You can now add a loop to Favorites”
Jira docs mention automation rules (e.g., automated reminders, rules that move work forward, Rovo AI automations) and integration-based automation triggers, which implies some scheduling capability, but no evidence explicitly describes a recurring/cron-style scheduled job or workflow trigger mechanism. Missing for 10: explicit documentation of a scheduled/recurring trigger (e.g., cron-like automation trigger), independent confirmation of reliability for scheduled automations, and details on limits/scope of such schedules.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Connect your tools to any Jira workflow with automation. Whether your team is using Bitbucket, Slack, or any other tool, automation keeps Ji…”
- [claimed-docs] “Connect your tools to any Jira workflow with automation.”
ai-native userVersion, review, and roll back my automations
weight 1 · round to LinearLinear offers general version history/checkpoint restore for work (linear-docs-35) and rich review tooling for agent-produced code changes (guided reviews, diff rendering — linear-docs-7, linear-docs-72), which partially satisfies the 'version, review, rollback' need for AI-generated work. However there is no evidence of version control, review, or rollback specifically for the automations/Loops themselves (the scheduled/event-driven workflows) — only their outputs (documents, code) get versioned. Missing for 10: explicit versioning of Loop/automation definitions, audit trail of automation changes, and a dedicated rollback mechanism for the automation logic itself rather than just its output artifacts.
- [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
- [claimed-docs] “Guided Reviews break diffs into focused sections with explainers on what changed and why.”
- [claimed-docs] “Images, fonts, Markdown, and PDFs now render directly inside Linear diffs.”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
Jiranone0/10No evidence in the pack addresses versioning, reviewing, or rolling back Jira automation rules; docs only mention creating automations via Rovo AI with no mention of change history or rollback capability. Missing for 10: any documentation of automation version history, audit/review workflow, or rollback mechanism.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Scale processes and save time with customizable workflows that integrate with your tech stack.”
Automation workflows — building automations — triggers, actions, branching, schedulingAutomation workflows
Building automations — triggers, actions, branching, scheduling
Ai task automation
ai-native userHave AI automatically triage and prioritize incoming bugs and tasks
weight 2 · round to LinearLinear docs explicitly describe AI-driven triage: incoming feedback/issues are 'instantly routed, labeled, and prioritized for the right team,' and Linear Agent can 'investigate and attempt a fix before it reaches an engineer,' plus a Priority tab surfaces what needs attention. These directly match the automatic triage/prioritization story. Missing for 10: independent/hands-on evidence validating triage accuracy or reliability beyond vendor changelog claims.
- [claimed-docs] “Automatically turn conversations and customer feedback into actionable issues that are instantly routed, labeled, and prioritized for the ri…”
- [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
- [claimed-docs] “The new Priority tab separates what needs your attention from what can wait, so something like a review blocking a release never gets buried…”
Rovo AI is documented to auto-assign tasks to the right person and use automation rules to move work forward, which is adjacent to triage, but there's no explicit documentation of AI automatically prioritizing or triaging incoming bugs/tasks by severity or urgency. Missing for 10: explicit bug-triage workflows, prioritization scoring/ranking by AI, and independent/hands-on evidence that Rovo AI performs this specific task.
- [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Use Rovo AI to identify trends to surface new opportunities and remove bottle necks.”
ai-native userHave my in-app AI assistant learn my tone, shorthand, and preferences to tailor its output
weight 1 · round drawnLinearnone0/10Evidence shows Linear Agent can draft updates, edit text, and run automated 'Loops', but nothing describes it learning an individual user's tone, shorthand, or personal preferences to tailor future outputs — personalization/memory of style is never mentioned.
Workflow automation
engineerAuto-generate a changelog for each release so shipping progress is easy to review
weight 1 · round to LinearLinear explicitly documents an auto-generate release notes option in pipeline settings, directly matching the story of auto-generating a changelog per release. missing for 10: no detail on customization/format of generated changelogs, no independent/hands-on corroboration beyond the single changelog entry.
- [claimed-docs] “Choose to auto-generate release notes in pipeline settings so your changelog is always up to date.”
Jiranone0/10No evidence of a release/changelog auto-generation feature in Jira; docs mention automation rules, integrations, and Rovo AI for status updates but nothing about generating changelogs from releases. Missing for 10: any documentation of release notes/changelog generation, version-based reporting export, or third-party changelog integration tied to Jira releases.
product managerBuild multi-step automations without writing code
weight 2 · round to LinearLinear's 'Loops' feature lets users describe a recurring job in plain language and choose a schedule or event trigger, with multi-step behavior like updating documents and posting Slack messages when conditions change—exactly a no-code automation builder usable by a PM. Additional context (skills, agent-based investigation/monitoring) reinforces no-code configurability. missing for 10: independent/hands-on evidence of a PM successfully building complex branching automations, and detail on conditional/branching logic depth
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Build agents that can investigate incidents, monitor SLAs, or analyze customer feedback.”
- [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
- [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
Jira's docs describe no-code automation capabilities: 'customizable workflows that integrate with your tech stack' (jira-docs-13), 'connect your tools to any Jira workflow with automation' (jira-intdir-1, jira-docs-22), and Rovo AI creating 'custom automations...from automated reminders to rules that move work forward' (jira-docs-4) — all pointing to rule-based, no-code automation building. Missing for 10: independent/hands-on corroboration of building multi-step trigger-condition-action automations, and detailed documentation of the automation rule builder's complexity/limits rather than marketing copy.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Scale processes and save time with customizable workflows that integrate with your tech stack.”
- [claimed-docs] “Connect your tools to any Jira workflow with automation. Whether your team is using Bitbucket, Slack, or any other tool, automation keeps Ji…”
- [claimed-docs] “Connect your tools to any Jira workflow with automation.”
- [claimed-docs] “Customizable fields, workflows, and more”
engineerBuild trigger-and-action automation rules to eliminate repetitive manual steps
weight 3 · round to LinearLinear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event, automating recurring work like updating docs, posting Slack messages, or monitoring initiatives — a direct trigger-and-action automation capability, further extensible via webhooks and the GraphQL API for custom automations. missing for 10: independent/hands-on verification of Loops reliability at scale, and more detail on the breadth of available trigger/action types beyond the examples shown.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
Vendor docs reference building automation that connects tools to Jira workflows and using Rovo AI to create custom rules (reminders, auto-moving work) which aligns with trigger-and-action automation, but the evidence pack lacks any independent/hands-on confirmation of Jira's no-code automation rule builder specifically, and community commentary never mentions the automation engine at all. Missing for 10: independent corroboration of the automation rule builder, concrete examples of trigger/condition/action configuration, and detail beyond marketing copy.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Connect your tools to any Jira workflow with automation. Whether your team is using Bitbucket, Slack, or any other tool, automation keeps Ji…”
- [claimed-docs] “Scale processes and save time with customizable workflows that integrate with your tech stack.”
- [claimed-docs] “Connect your tools to any Jira workflow with automation.”
engineerCreate a workflow that runs on a schedule or recurring event to handle routine team work
weight 2 · round to LinearLinear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event, targeting recurring team work like weekly planning, doc updates, or launch plan syncing (linear-docs-11, linear-docs-36, linear-docs-23, linear-docs-95, linear-docs-96, linear-docs-100). This directly matches the story of scheduled/recurring workflow automation for routine team tasks. missing for 10: independent/hands-on verification of Loops reliability and no detail on error handling or monitoring of scheduled runs.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
Jira's marketing docs mention customizable, automatable workflows and Rovo AI-driven automation rules ('automated reminders to rules that move work forward'), implying some rule-based automation capability, but no evidence explicitly describes scheduled/cron-based or recurring-event triggers for routine tasks. Missing for 10: explicit documentation of schedule-based automation triggers, hands-on confirmation of recurring automations working reliably, and independent corroboration beyond vendor marketing copy.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Scale processes and save time with customizable workflows that integrate with your tech stack.”
- [claimed-docs] “Customizable fields, workflows, and more”
ai-native userWhat happens—extra charges, throttling, or a hard stop—when I exceed my plan's automation or API call limits
weight 3 · round to LinearLinear's docs publish exact per-auth-type API rate limits, response headers (e.g. X-RateLimit-Requests-Limit) and a leaky-bucket refill model, and separately allow admins to set spend limits for AI agent/automation usage that reset periodically — together these give a user real visibility into automation/API limits. However, the pack doesn't explicitly spell out the concrete consequence of exceeding a limit (e.g. exact 429 throttling behavior, whether overages incur extra charges, or a hard stop for automation/Loops usage), so the full 'what happens when I exceed' picture is only partially documented. Missing for 10: explicit statement of throttling/error response code, confirmation of no/optional overage billing, and documented consequence for exceeding automation (Loops/agent) usage specifically rather than just spend caps.
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Admins can also set workspace-wide and per-user spend limits that reset daily, weekly, or monthly.”
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration
Working as a team — sharing, comments, roles, simultaneous editing
Cross tool sync
designerKeep project status updated from my design tool without switching apps
weight 2 · round to JiraLinearnone0/10The evidence pack shows Linear's API, webhooks, GraphQL SDK, and general integrations (GitHub, Slack, Okta) but contains no mention of a Figma or other design-tool plugin/integration that lets designers update project status without leaving their design tool. Missing for 10: any Figma/design-tool plugin, any documented design-tool-to-Linear status sync, or third-party evidence of such a workflow.
Atlassian's marketing page explicitly claims Jira lets you 'track progress from your favorite tools like Slack, Figma and Gmail' (jira-docs-2), which directly supports the story, but this is a single vendor bullet with no dedicated documentation of how the Figma sync works and no independent or hands-on confirmation from designers. Community evidence even notes friction with design teams adopting Jira workflows (jira-comm-13), reinforcing that this remains a thin, unverified claim rather than a proven capability. Missing for 10: dedicated Figma-integration docs/screenshots, independent hands-on validation, and confirmation designers can update status without leaving Figma.
- [claimed-docs] “Keep work up-to-date by tracking progress from your favorite tools like Slack, Figma and Gmail powered by an AI-assist”
- [community] “Once a JIRA shop, we moved everything to Asana years ago, after trying literally everything else. Our design team just could not get on boar…”
Docs knowledge
product managerCreate and organize shared docs and notes alongside my project work
weight 3 · round to LinearLinear supports document creation and organization tied to projects/issues (teams can create documents from home page, add existing documents to projects/issues, group into sections, comment on docs, mobile doc editing) which covers shared docs alongside project work. However, evidence for cross-team/workspace-wide doc organization, folder hierarchies, or dedicated doc search/collaboration features (e.g. co-editing, version history for docs specifically) is thin. missing for 10: evidence of broader doc organization features (folders/wikis beyond project linkage), real-time co-editing, and independent user feedback confirming docs experience.
- [claimed-docs] “Teams can create documents directly from their home page, add existing documents from projects and issues, and group resources into sections…”
- [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”
- [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
- [claimed-docs] “Use callout components to draw attention to important information in issue and project descriptions, as well as documents.”
Jiranone0/10The evidence pack shows Jira as an issue/work tracker with customizable workflows, boards, and integrations, but contains no mention of a native shared docs/notes feature within Jira itself; the only related reference is community complaint about Confluence-Jira ticket creation breaking, which is not a documented docs capability.
- [community] “Why do I need to mark an epic as closed two different ways? Why is it really difficult to see what tickets were in a closed sprint? Why is i…”
In context discussion
engineerComment directly on specific text or images within an item's description
weight 2 · round to LinearLinear's own changelog explicitly states the exact capability: 'You can now comment directly on text or images in issue descriptions,' directly matching the story. missing for 10: no independent/hands-on corroboration beyond the vendor changelog entry.
- [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
Jiranone0/10No evidence in the pack describes inline/anchored commenting on specific text or images within a description field (e.g., text-selection comments or image annotations); only general commenting via ticket fields is implied by unrelated features. Missing for 10: any documentation or mention of text-anchored or image-annotation commenting functionality.
Real time sync
engineerSee teammates' changes reflected instantly across open sessions without refreshing
weight 3 · round drawnLinearnone0/10The evidence pack contains no documentation or community reports describing real-time, no-refresh syncing of teammates' changes across open sessions (e.g., live cursors, instant issue updates, presence). References to webhooks (linear-docs-51/52) describe external HTTP push notifications for integrations, not in-app live UI updates, and speed-related comments (linear-comm-6) address load times, not multi-session sync.
Jiranone0/10No vendor documentation or community evidence describes live/real-time propagation of teammate changes without a manual refresh; the feature pages focus on views, workflows, and integrations, not real-time sync. Some community reports even describe reload loops and stale UI behavior, but nothing confirms or denies instant cross-session updates specifically.
- [claimed-docs] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”
- [community] “Why do I need to mark an epic as closed two different ways? Why is it really difficult to see what tickets were in a closed sprint? Why is i…”
- [community] “I routinely lose data in jira, like saving errors. Dragging and dropping attachments sometimes causes the page to crash and reload. Everythi…”
Team chat
engineerChat with my team directly inside the same tool I plan work in
weight 2 · round to LinearLinear supports asynchronous team collaboration via comments on issues, documents, and images (linear-docs-24, linear-docs-22) and @mentions (linear-docs-54), plus Slack integration for notifications (linear-docs-61, linear-docs-81), but there is no evidence of a native real-time chat/messaging feature inside Linear itself — collaboration is comment-based, not conversational chat. missing for 10: a dedicated in-app chat/messaging surface, evidence of synchronous team chat, and any first-party claim positioning Linear as a chat tool rather than relying on comments/Slack.
- [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
- [claimed-docs] “Teams can create documents directly from their home page, add existing documents from projects and issues, and group resources into sections…”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
- [claimed-docs] “Create issues from Slack messages and sync threads”
Jiranone0/10Evidence shows Jira integrates with Slack and other tools for notifications/automation, but there is no evidence of a native chat/messaging feature inside Jira itself where engineers can converse directly while planning work; the integrations point users out to Slack rather than providing in-tool chat.
- [claimed-docs] “Keep work up-to-date by tracking progress from your favorite tools like Slack, Figma and Gmail powered by an AI-assist”
- [claimed-docs] “Connect your tools to any Jira workflow with automation. Whether your team is using Bitbucket, Slack, or any other tool, automation keeps Ji…”
- [claimed-docs] “Choose from the over 3000+ integrations available in the Atlassian Marketplace.”
Integrations — connecting to other tools — breadth and depth of built-in integrationsIntegrations
Connecting to other tools — breadth and depth of built-in integrations
App ecosystem
engineerKeep tasks bi-directionally synced with my code repository's issue tracker instead of duplicating data
weight 2 · round drawnLinear's changelog references GitHub-synced issues (opening them in GitHub) and syncing review requests/teams with GitHub, plus a public GraphQL API and webhooks that could be used to build two-way sync with an external tracker, but there is no explicit documentation describing full bi-directional field sync (status, description, comments) that eliminates duplicate data entry with a repo issue tracker. Missing for 10: explicit doc/feature description of two-way sync with GitHub Issues (not just PR/review linking), independent/hands-on confirmation that sync avoids duplication, and coverage beyond GitHub (e.g., GitLab).
- [claimed-docs] “Open a GitHub-synced issue in GitHub with OG”
- [claimed-docs] “You can now assign reviews to GitHub teams.”
- [claimed-docs] “You can now assign reviews to GitHub teams. Review requests assigned to your GitHub teams appear in a dedicated section of the Reviews inbox…”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
Jira documents integration with Bitbucket (dev status visibility, release correlation) and a broad marketplace/automation ecosystem (3000+ apps) that could sync with code repo issue trackers like GitHub, but the evidence pack lacks specifics on true bi-directional sync mechanics (e.g., how issue state changes flow both ways, conflict resolution) for non-Atlassian repos like GitHub/GitLab. missing for 10: concrete bi-directional sync documentation with major non-Atlassian repo trackers (GitHub Issues, GitLab), independent verification that sync avoids data duplication, and details on conflict/latency handling.
- [claimed-docs] “Teams that integrate Jira Software with Bitbucket release versions 14% more often than those who don't.”
- [claimed-docs] “View development status without leaving Jira”
- [claimed-docs] “Connect your tools to any Jira workflow with automation. Whether your team is using Bitbucket, Slack, or any other tool, automation keeps Ji…”
- [claimed-docs] “Choose from the over 3000+ integrations available in the Atlassian Marketplace.”
- [claimed-docs] “Tempo Timesheets, Zephyr, and over 3,000 other apps ensure Jira Software can be custom tailored to fit any and every use case.”
engineerSee my assigned tasks from multiple project management tools in one unified view
weight 2 · round drawnLinearnone0/10Evidence shows Linear integrates with GitHub, Slack, Okta, and supports one-time data import from other services (linear-docs-47), but there is no evidence of a unified cross-tool task view aggregating assignments from multiple external project management tools (e.g., Jira, Asana) into one dashboard. Linear positions itself as a replacement for such tools rather than an aggregator.
- [claimed-docs] “Import data from other services into Linear”
Jiranone0/10Evidence shows Jira has a marketplace with 3000+ integrations and can track updates from tools like Slack, Figma, Gmail, but there is no evidence of a unified view that aggregates an engineer's assigned tasks specifically from other project management tools (e.g., Asana, Trello, Monday) into one dashboard.
- [claimed-docs] “Choose from the over 3000+ integrations available in the Atlassian Marketplace.”
- [claimed-docs] “Keep work up-to-date by tracking progress from your favorite tools like Slack, Figma and Gmail powered by an AI-assist”
engineerConnect common tools like Slack, GitHub, and Google Drive natively
weight 2 · round to LinearLinear's integrations directory explicitly documents native Slack (create issues from Slack messages, sync threads, Slack notifications), GitHub (automate PR workflows, review code, sync issues, assign reviews to GitHub teams), and Google Drive-adjacent file referencing plus a broad app ecosystem (Figma, GitLab, Sentry, Datadog, Notion, etc.), backed by OAuth/API infrastructure for deeper connections. Missing for 10: explicit first-party documentation of a native Google Drive integration specifically (only general file/import references appear) and independent hands-on confirmation of these integrations' reliability.
- [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
- [claimed-docs] “Create issues from Slack messages and sync threads”
- [claimed-docs] “You can now assign reviews to GitHub teams.”
- [claimed-docs] “You can now assign reviews to GitHub teams. Review requests assigned to your GitHub teams appear in a dedicated section of the Reviews inbox…”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
- [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
- [claimed-docs] “Learn how to reference a file in markdown content, or upload with the API”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
Jira docs confirm native/marketplace integrations with Slack, Bitbucket, Trello, and 3000+ apps, plus explicit mention of Slack automation triggers, but GitHub is not explicitly named (only Bitbucket) and Google Drive integration is not mentioned at all (Gmail/Figma/Confluence are cited instead). missing for 10: explicit GitHub integration evidence, explicit Google Drive integration evidence, independent/hands-on confirmation of these specific integrations working well.
- [claimed-docs] “Keep work up-to-date by tracking progress from your favorite tools like Slack, Figma and Gmail powered by an AI-assist”
- [claimed-docs] “Choose from the over 3000+ integrations available in the Atlassian Marketplace.”
- [claimed-docs] “Teams that integrate Jira Software with Bitbucket release versions 14% more often than those who don't.”
- [claimed-docs] “Collaborate across tools with transparency and create workflows that work for you by syncing Trello and Jira Software.”
- [claimed-docs] “Tempo Timesheets, Zephyr, and over 3,000 other apps ensure Jira Software can be custom tailored to fit any and every use case.”
- [claimed-docs] “Connect your tools to any Jira workflow with automation. Whether your team is using Bitbucket, Slack, or any other tool, automation keeps Ji…”
product managerConnect my workspace to thousands of third-party tools via an app marketplace
weight 2 · round to JiraLinear ships a documented integrations/app directory (GitHub, Slack, Figma, Salesforce, Sentry, Datadog, Notion, Airbyte, Fivetran, Cursor, ChatGPT, Claude, Jira migration, etc.), an OAuth app creation flow, and admin-level third-party app approval controls, which together function like a marketplace for connecting external tools. However, the evidence shows a curated directory of a few dozen named integrations plus a general public GraphQL/OAuth API for building custom ones, not literally 'thousands' of pre-built marketplace apps as the story implies. Missing for 10: evidence of marketplace scale (thousands of listed apps), a searchable public app store UI, and independent confirmation of ecosystem breadth beyond Linear's own docs.
- [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
- [claimed-docs] “Create issues from Slack messages and sync threads”
- [claimed-docs] “Create and link issues directly from Figma”
- [claimed-docs] “Automate your Merge Request workflow”
- [claimed-docs] “Build custom dashboards and analytics from issue and project data”
- [claimed-docs] “Delegate issues to Codex directly from Linear”
- [claimed-docs] “Turn issues into pull requests with Cursor cloud agents”
- [claimed-docs] “Automate work from issue to tested PR with Devin”
- [claimed-docs] “Create Linear issues from Datadog Cases and Monitors”
- [claimed-docs] “Smoothly transition from Jira to Linear”
- [claimed-docs] “Sync your Linear data with the Fivetran connector”
- [claimed-docs] “Create Linear issues from Salesforce cases”
- [claimed-docs] “Connect Linear to Airbyte and consolidate data in data warehouses, lakes, and databases”
- [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
- [claimed-docs] “Use URL parameters to send users directly to a pre-filled Create OAuth App form in Linear. An equivalent JSON manifest format lets you store…”
Atlassian Marketplace is explicitly documented with '3000+ integrations' and named examples (Slack, Figma, Gmail, Bitbucket, Trello, Tempo, Zephyr), directly matching the story. Missing for 10: independent/hands-on verification of marketplace breadth or ease of installing apps beyond vendor claims.
- [claimed-docs] “Choose from the over 3000+ integrations available in the Atlassian Marketplace.”
- [claimed-docs] “Tempo Timesheets, Zephyr, and over 3,000 other apps ensure Jira Software can be custom tailored to fit any and every use case.”
- [claimed-docs] “Keep work up-to-date by tracking progress from your favorite tools like Slack, Figma and Gmail powered by an AI-assist”
- [claimed-docs] “Teams that integrate Jira Software with Bitbucket release versions 14% more often than those who don't.”
- [claimed-docs] “Collaborate across tools with transparency and create workflows that work for you by syncing Trello and Jira Software.”
- [claimed-docs] “Extend Jira Software with apps”
Extensibility
designerBuild custom views and dashboard widgets that feel native to the product
weight 1 · round drawnLinearnone0/10Evidence only shows saved/shareable filtered views (linear-docs-13) and standard issue/project views — there is no SDK, embed framework, or dashboard-widget builder that would let a designer create custom native-feeling widgets or dashboards. The public API/webhooks/SDK docs (linear-docs-49-53) are developer-facing data access, not a UI customization surface for designers.
Jiranone0/10Evidence only shows built-in view switching (boards/lists/timeline/calendar) and a large marketplace of integrations, but nothing about a designer-facing SDK, UI kit, or dashboard/gadget-building framework that lets a designer construct custom widgets or views that feel native to Jira. Missing for 10: evidence of Forge/Connect UI kit or gadget API for custom dashboard widgets, design system/component library for building native-feeling views, and any case study of designers building such extensions.
- [claimed-docs] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”
- [claimed-docs] “Choose from the over 3000+ integrations available in the Atlassian Marketplace.”
- [claimed-docs] “Global and project-level configuration”
Onboarding — getting started and time-to-first-value storiesOnboarding
Getting started and time-to-first-value stories
Getting started
product managerThat exporting my workspace preserves full history—comments, attachments, and audit trails—not just task titles
weight 3 · round drawnLinearnone0/10The evidence pack contains no mention of a workspace export feature at all—only import tooling (from other services into Linear) is documented, with nothing about exporting comments, attachments, or audit trails out of Linear. This is a fair question for a project-management tool, so absence of evidence means 'none' rather than 'na'.
- [claimed-docs] “Import data from other services into Linear”
- [claimed-docs] “Import tooling for uploading from other systems”
engineerFollow a guided walkthrough to set up my workspace the first time
weight 1 · round drawnLinearnone0/10No evidence describes an onboarding wizard, guided workspace setup, or first-run tutorial for new engineers; the pack covers agents, integrations, API docs, and changelog features but nothing about initial workspace configuration guidance.
Jiranone0/10No evidence of a guided onboarding walkthrough or setup wizard for first-time workspace configuration; evidence only covers features, integrations, and general community sentiment (some complaints about confusing UX). Missing for 10: any first-party documentation of an onboarding/setup wizard, guided tour, or first-run experience for engineers.
product managerImport my data from another tool when switching over
weight 2 · round to LinearLinear documents explicit import capabilities: generic 'Import data from other services into Linear' plus a dedicated Jira migration flow ('Smoothly transition from Jira to Linear') and import tooling for uploading from other systems mentioned in the repo README. This directly satisfies the PM's need to migrate data when switching tools, though detail is thin — missing for 10: specifics on which tools/formats are supported, what data (comments, attachments, custom fields) is preserved, and independent/community confirmation that migrations work smoothly in practice.
- [claimed-docs] “Import data from other services into Linear”
- [claimed-docs] “Import tooling for uploading from other systems”
- [claimed-docs] “Smoothly transition from Jira to Linear”
Jiranone0/10The evidence pack contains no mention of import tools, migration wizards, or CSV/data import features from other project management tools; it only covers integrations, automation, and general feature marketing plus community complaints unrelated to import/migration. Absence of evidence for this applicable onboarding capability yields 'none'.
product managerJumpstart a new project using pre-built templates
weight 2 · round to JiraLinearnone0/10The evidence pack contains no mention of pre-built project or issue templates for jumpstarting new projects; the closest feature, the 'project composer' with Linear Agent, is AI-assisted drafting rather than a template library. missing for 10: any documentation of a templates gallery, template selection UI, or first-party/community evidence of template-based project creation.
Jira's vendor docs explicitly claim pre-built, customizable templates for any project type (agile, marketing, etc.), directly matching the story. No independent/hands-on corroboration or specifics on template variety/quality is present, and no community evidence discusses templates specifically. Missing for 10: independent verification of template quality/breadth, hands-on onboarding experience evidence.
- [claimed-docs] “Start fast with pre-built and customizable templates for any project, from agile sprints to marketing campaigns.”
Pricing transparency
product managerWhether my plan enforces a minimum seat count or annual billing commitment before I subscribe
weight 3 · round drawnLinearnone0/10No evidence in the pack addresses pricing plans, seat minimums, or annual billing commitments for Linear's subscription plans; all evidence relates to product features, API, and integrations. Missing for 10: any pricing page or plan documentation disclosing seat minimums, billing cadence, or contract terms.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to LinearLinear's GraphQL API exposes the same schema used internally to build the app, with full introspection, mutations for issues/projects/comments, webhooks, OAuth2/API key auth, and an SDK, covering most core CRUD and workflow operations (linear-docs-49, linear-supp-graphql-introspection, linear-docs-74, linear-docs-92-93). However, several UI-native features (Agent sessions/Loops orchestration nuances, admin spend limits, Okta/SSO provisioning, third-party app approval flows, mobile-specific review UI) are not clearly exposed as API-first operations, and no independent evidence confirms 1:1 parity between UI and API surfaces. missing for 10: explicit documentation/confirmation that all admin/security settings (SSO, spend limits, app approvals) and newer Agent/Loop features are fully API-controllable, plus independent verification of full UI-API parity.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
- [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
Jira is documented to have 'Rich APIs' and community members confirm using the REST API/JQL for real workflows (bug submission scripts, querying data), showing the API is functional and used in practice. However, there is no evidence of comprehensive UI/API parity, and probes show no discoverable OpenAPI spec or llms.txt, undermining verifiability of full coverage. Missing for 10: explicit parity documentation, discoverable OpenAPI/machine-readable spec, and confirmation that all UI actions (workflow config, admin settings, boards) are API-accessible.
- [claimed-docs] “Rich APIs”
- [community] “Due to the slow loading, I ended up writing some simple Jira API wrapper scripts for submitting bug reports quicker in our systems.”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Does Plane offer an alternative for JQL (Jira Query Language)? That's what I appreciate most about Jira.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developer.atlassian.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.atlassian.com/openapi.json, https://developer.atlassian.com/swagger.json, https://…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to LinearLinear has no documented one-click 'export all data' feature; however, its open GraphQL API (with full schema introspection, SDK, and reasonable rate limits) lets a technical user programmatically pull out all their issues, projects, and comments, which is a de facto exit path. There's no bulk-export or archive format documented, and community confirms no self-hosting option, meaning a full clean 'leave with your data' workflow is not officially supported. missing for 10: a documented bulk/archival export feature (e.g., JSON/CSV dump), official data-portability tooling, and independent confirmation that a full account export actually works.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”
Jiranone0/10The evidence pack shows Jira has REST APIs and integrations (jira-docs-1, jira-comm-16) but contains no documentation of a dedicated full-data export feature or explicit support for open, portable formats (e.g., CSV/XML/JSON full backup) that would let a user extract everything and leave. Missing for 10: documented full-account/data export tool, explicit open-format export (CSV/XML/JSON), data portability/backup guarantees, and any community confirmation of successful full export and migration.
- [claimed-docs] “Rich APIs”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
ai-native userRead the product's source under an open license
weight 2 · round drawnLinearnone0/10No evidence indicates Linear's application source is published under an open license; the only related item is a stray README reference on GitHub (linear-docs-101) which does not establish an open-source license or full source availability. Linear is a closed, proprietary SaaS product per all other evidence (docs, integrations, community threads about lack of self-hosting).
- [claimed-docs] “Import tooling for uploading from other systems”
- [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”
ai-native userSelf-host the core product
weight 3 · round to JiraLinearnone0/10Linear is explicitly a cloud-only SaaS with no self-hosting option; a community Q&A cites a direct Linear response stating 'We unfortunately don't currently have plans to provide self-hosting' (linear-comm-10). No docs anywhere in the evidence pack mention on-prem/self-hosted deployment.
- [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”
Only evidence is a community comment mentioning running Jira on-prem, implying a self-hosted option exists but with performance caveats (e.g., Lucene index issues); there is no first-party documentation of a self-hosted/open-source edition, licensing, or install instructions in the pack. missing for 10: official self-hosting/Data Center documentation, deployment guides, licensing terms, independent corroboration of feature parity with cloud.
- [community] “Also it's really annoying when I try to copy something from a ticket description but it starts editing the whole description field.”
Planning tracking — planning and tracking work — issues, sprints, boards, statusPlanning tracking
Planning and tracking work — issues, sprints, boards, status
Mobile access
engineerManage my tasks from a full-featured native mobile app without missing desktop functionality
weight 2 · round to LinearDocs show mobile app supports specific engineer workflows like reviewing code diffs and commenting (linear-docs-6) and, as of a recent update, document creation/editing (linear-docs-71), indicating mobile parity is being actively built out rather than already complete. There is no evidence of full task-management parity (e.g., initiatives, project views, filters, admin settings) on mobile, and no independent/community confirmation of a full-featured mobile experience. Missing for 10: comprehensive mobile feature-parity documentation covering all core desktop workflows (initiatives, filters, admin, integrations), and independent user reviews confirming no functionality gaps on mobile.
- [claimed-docs] “Use the Linear mobile app to review code changes, comment on specific lines, and iterate with Linear Agent.”
- [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”
Jiranone0/10No evidence in the pack mentions a native mobile app, its feature parity with desktop, or mobile-specific functionality at all; all citations concern web features, integrations, and general community sentiment. Missing for 10: any mention of a mobile app, its feature set, offline capability, or comparisons to desktop functionality.
Task management
product managerTrack cross-team dependencies to coordinate large launches
weight 2 · round to JiraLinear's initiative feature lets a team be assigned to lead cross-team work with statuses (proposed/canceled) and priority, which supports coordinating large launches (linear-docs-4, linear-docs-14, linear-docs-37, linear-docs-63, linear-docs-76), and project-view subscriptions notify on changes (linear-docs-61). However, there's no explicit evidence of dependency-specific features like blocking/blocked-by issue relations or a dependency graph across teams. missing for 10: explicit issue-to-issue dependency/blocking relation docs, cross-team dependency visualization, hands-on evidence of coordinating a large launch using these features.
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
- [claimed-docs] “Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
- [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
Jira docs explicitly claim cross-team dependency coordination for launches (jira-docs-8) plus supporting visibility/tracking features (timelines, progress views, priority visibility) that align with dependency tracking, and community evidence corroborates real-world use of Jira for tracking work via boards/JQL/REST. However, no dedicated 'dependency linking' feature or cross-project roadmap capability is directly evidenced, and community feedback highlights usability friction (slow, confusing UI, workflow issues) that could hamper coordination at scale. Missing for 10: explicit evidence of dependency-linking/blocked-by features, cross-project roadmap tooling, and independent validation of large-launch coordination use cases.
- [claimed-docs] “Connect engineering, product, and marketing initiatives to coordinate big launches across every team.”
- [claimed-docs] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”
- [claimed-docs] “Get visibility on your company's progress towards top priorities as projects advance”
- [community] “Jira has always been very quick and responsive for me. It offers a good amount of customization too... Never once encountered a major bug in…”
- [community] “Jira is bloated. Full stop. It feels like there isn't a strong unified product vision for Jira. It's just trying to solve everything.”
- [community] “Please, kill Jira and Confluence. I hate Atlassian tools so much. The user interfaces are sluggish no matter the hardware you're using... it…”
product managerCustomize fields and workflow statuses to match my team's process
weight 2 · round to JiraLinearnone0/10The evidence pack contains no vendor documentation describing custom issue fields or configurable workflow statuses for teams; the only relevant community evidence explicitly states Linear lacks the ability to define different issue types or add custom fields, and describes this as a deliberate design choice against Jira-style customization.
Vendor docs explicitly promise customizable fields, workflows, and global/project-level configuration (jira-docs-3, jira-docs-13, jira-docs-16), and one community reviewer confirms Jira offers 'a good amount of customization' (jira-comm-1). However another hands-on comment describes the workflow/transition model as 'fundamentally flawed' and overly rigid (jira-comm-3), and others cite confusing setup and bloat (jira-comm-9, jira-comm-12), suggesting the customization is powerful but hard to configure cleanly. Missing for 10: independent verification of field/workflow customization UX, and resolution of the workflow-rigidity complaints.
- [claimed-docs] “Customizable fields, workflows, and more”
- [claimed-docs] “Scale processes and save time with customizable workflows that integrate with your tech stack.”
- [claimed-docs] “Global and project-level configuration”
- [community] “Jira has always been very quick and responsive for me. It offers a good amount of customization too... Never once encountered a major bug in…”
- [community] “Jira is heavy and slow - its model of limited transitions is fundamentally flawed, encouraging micromanagement and making mistakes hard to u…”
- [community] “Jira is bloated. Full stop. It feels like there isn't a strong unified product vision for Jira. It's just trying to solve everything.”
product managerTrack initiatives with status, priority, and an owning team
weight 2 · round to LinearLinear docs show initiatives support status (Proposed/canceled/other statuses), priority, and an owning team assignment ('assign a team to lead an initiative'), directly matching the story. missing for 10: independent hands-on corroboration of the initiative-tracking UI beyond changelog claims.
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work and how it contributes to the broad…”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
- [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
Jira's customizable fields/workflows, timeline/board views, and cross-team initiative coordination (jira-docs-3, jira-docs-8, jira-docs-11, jira-docs-14) directly support tracking initiatives with status, priority, and owning team, and this is a core, long-standing Jira use case reinforced by community mentions of its flexibility (jira-comm-1, jira-comm-16). Missing for 10: explicit documentation of an 'Initiative' issue type/hierarchy level and independent hands-on confirmation of initiative-level tracking specifically (vs. general issue tracking).
- [claimed-docs] “Customizable fields, workflows, and more”
- [claimed-docs] “Connect engineering, product, and marketing initiatives to coordinate big launches across every team.”
- [claimed-docs] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”
- [claimed-docs] “Get visibility on your company's progress towards top priorities as projects advance”
- [claimed-docs] “Global and project-level configuration”
- [community] “Jira has always been very quick and responsive for me. It offers a good amount of customization too... Never once encountered a major bug in…”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
engineerPlan and manage sprints for agile software development
weight 2 · round to JiraEvidence shows Linear supports general agile planning artifacts—issues, priorities, initiatives, roadmaps, and project alignment (linear-docs-76, linear-docs-63, linear-docs-37)—and community comments confirm it functions as a fast issue tracker (linear-comm-1, linear-comm-6). However, the pack contains no direct evidence of Linear's sprint/cycle-specific features (e.g., cycle planning, sprint velocity, burndown, backlog grooming) that would confirm dedicated sprint management. Missing for 10: explicit documentation of Cycles/sprint creation, velocity tracking, sprint retrospectives, and backlog prioritization tools.
- [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
- [claimed-docs] “Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
- [community] “We've been using Linear for a couple months. It's kind of like Superhuman in that the primary benefit is hotkeys. Otherwise it is an issue t…”
- [community] “Can't speak for other teams... but we migrated from JIRA to Linear for our small team, and haven't looked back. Just the simple fact that it…”
Jira's docs explicitly market agile sprint templates, boards/timeline views, and burndown/cycle-time tracking (jira-docs-5, jira-docs-9, jira-docs-11), directly supporting sprint planning and management. However, community feedback includes specific friction with sprint mechanics, e.g. difficulty seeing tickets from a closed sprint and general UI slowness/bugginess (jira-comm-10, jira-comm-3, jira-comm-9), tempering the polish of the delivered experience. Missing for 10: independent hands-on validation specifically of sprint planning workflows (backlog grooming, sprint velocity) beyond marketing copy, and resolution of the closed-sprint visibility complaint.
- [claimed-docs] “Start fast with pre-built and customizable templates for any project, from agile sprints to marketing campaigns.”
- [claimed-docs] “Keep work on track whether you're measuring engineering cycle time, burn down charts, or managing capacity.”
- [claimed-docs] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”
- [community] “Why do I need to mark an epic as closed two different ways? Why is it really difficult to see what tickets were in a closed sprint? Why is i…”
- [community] “Jira is heavy and slow - its model of limited transitions is fundamentally flawed, encouraging micromanagement and making mistakes hard to u…”
engineerCreate tasks and assign them to teammates with due dates
weight 3 · round to JiraEvidence confirms issue creation (IssueCreate mutation) and assignment (assignedIssues, agents 'delegated issues through assignment') as core API/product capabilities, implying basic task creation and assignment support, but no evidence pack item explicitly documents setting or displaying due dates on issues. Missing for 10: explicit documentation of a due-date field on issues, UI walkthrough of assigning a task with a due date, and independent confirmation of this specific workflow.
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [community] “I have used Linear on a couple of my hobby projects and it's a great tool to quickly capture features and bugs. My one gripe... is that the …”
Jira's core workflow includes creating issues/tasks and assigning them to teammates, corroborated by docs (jira-docs-10) and community usage evidence of assignment (jira-comm-2, jira-comm-7). Due dates are a standard Jira field but not explicitly called out in the evidence pack. Missing for 10: explicit documentation/mention of due-date field usage, independent hands-on confirmation of due-date workflows.
- [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
- [claimed-docs] “Customizable fields, workflows, and more”
- [community] “Biggest problem when I used it, could not assign anything to more than 1 person.”
- [community] “As a developer, once I finish my ticket I assign it to a QA. Then I can never get back to the ticket... completed tickets aren't assigned to…”
engineerBreak work into subtasks and link dependent tasks so blocking order is clear
weight 3 · round to JiraLinearnone0/10The evidence pack contains no mention of sub-issues, issue hierarchies, or blocking/blocked-by dependency links—core planning-tracking features one would expect docs to cover for an issue tracker. Nothing here cites Linear's sub-issue or relation functionality, so this applicable axis is unsupported by the given evidence.
jira-docs-10 shows Jira supports breaking big work into actionable tasks (subtask-like breakdown), but the evidence pack contains no explicit mention of issue linking types (e.g., 'blocks'/'is blocked by') or dependency visualization that makes blocking order clear. Missing for 10: documentation of issue-link types for dependencies, evidence of dependency visualization (e.g., timeline/dependency lines), and any hands-on confirmation of this specific workflow.
- [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
- [claimed-docs] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”
engineerLog time directly against tasks and projects
weight 2 · round drawnLinearnone0/10No evidence in the pack mentions time tracking, time logging, or timesheet functionality against tasks/projects in Linear; the evidence focuses on issue tracking, agents, coding sessions, and planning features.
Jiranone0/10The evidence pack contains no citation mentioning time tracking, worklogs, or logging time against tasks/projects—only generic feature marketing (workflows, AI-assist, integrations) and community complaints unrelated to time logging. Missing for 10: any docs or community evidence confirming time-logging/worklog functionality.
Views organization
engineerHow the product performs and whether item caps apply in workspaces with tens of thousands of tasks
weight 2 · round drawnLinearnone0/10No evidence pack item addresses performance benchmarks, scalability limits, or item caps for workspaces with tens of thousands of tasks; community comments only mention general speed vs Jira without scale specifics. This is a fair question for an issue tracker but remains unaddressed here.
Jiranone0/10No vendor documentation addresses item caps or performance benchmarks at tens-of-thousands-of-tasks scale; community comments are anecdotal and contradictory (some call Jira 'quick and responsive' while many others describe it as slow, bloated, and prone to reload loops) without concrete data on scaling limits.
- [community] “Jira has always been very quick and responsive for me. It offers a good amount of customization too... Never once encountered a major bug in…”
- [community] “Jira is heavy and slow - its model of limited transitions is fundamentally flawed, encouraging micromanagement and making mistakes hard to u…”
- [community] “Why do I need to mark an epic as closed two different ways? Why is it really difficult to see what tickets were in a closed sprint? Why is i…”
- [community] “Please, kill Jira and Confluence. I hate Atlassian tools so much. The user interfaces are sluggish no matter the hardware you're using... it…”
engineerSwitch between board, list, calendar, and timeline views of the same work
weight 2 · round to JiraLinearnone0/10The evidence pack has no mention of board, list, calendar, or timeline views, or of switching between them — only a generic reference to sharing 'any filtered view' via URL, which doesn't establish this specific multi-view capability.
jira-docs-11 explicitly confirms switching between boards, lists, timeline, and calendar views of the same work, which directly matches the story; general performance/UX complaints in community evidence do not contradict this specific capability. Missing for 10: independent hands-on confirmation specifically of the view-switching feature (community evidence focuses on other pain points, not this capability).
- [claimed-docs] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”
engineerSave a filtered view of work and share it with a link
weight 2 · round to LinearLinear explicitly documents saving/sharing filtered views: "You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop" (linear-docs-13), directly matching the story of sharing a filtered work view via link. Missing for 10: independent/hands-on community confirmation of this specific feature beyond the vendor changelog.
- [claimed-docs] “You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop.”
Community comments confirm Jira's JQL/saved-search functionality exists and is valued by some users (jira-comm-16, jira-comm-17), but another user reports that creating a useful saved search is 'so painful' (jira-comm-12), indicating significant UX friction rather than a broken feature. No first-party documentation in the pack explicitly describes saving a filtered view and sharing it via a link. Missing for 10: official docs on saved filter creation/sharing, hands-on confirmation that the share-link mechanism works smoothly, and resolution of the friction noted by users.
- [community] “Trying to do something as seemingly simple as create a useful saved search in JIRA is so painful I can't imagine its creation was not an act…”
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Does Plane offer an alternative for JQL (Jira Query Language)? That's what I appreciate most about Jira.”
engineerSearch across all tasks, docs, and comments and get fast, accurate results
weight 2 · round to JiraLinearnone0/10The evidence pack contains no documentation or community commentary about a search feature spanning issues, docs, and comments, nor any claims about speed or accuracy of such search — only filtering/view-sharing and speed-of-loading tickets are mentioned, which is a different capability.
Community feedback shows engineers value querying Jira data via JQL/REST (jira-comm-16, jira-comm-17), suggesting some search capability exists, but there's no evidence of unified search across tasks, docs, and comments, and other users report that creating even a basic saved search is painful (jira-comm-12) and that the UI is frequently slow (jira-comm-3, jira-comm-10, jira-comm-15). Missing for 10: dedicated documentation on a unified search feature, evidence of searching docs/comments alongside tasks, and independent confirmation of search speed/accuracy.
- [community] “One of the things I like most about Jira is the ability to execute useful queries via REST on the data stored in there.”
- [community] “Does Plane offer an alternative for JQL (Jira Query Language)? That's what I appreciate most about Jira.”
- [community] “Trying to do something as seemingly simple as create a useful saved search in JIRA is so painful I can't imagine its creation was not an act…”
- [community] “Jira is heavy and slow - its model of limited transitions is fundamentally flawed, encouraging micromanagement and making mistakes hard to u…”
- [community] “Why do I need to mark an epic as closed two different ways? Why is it really difficult to see what tickets were in a closed sprint? Why is i…”
- [community] “Please, kill Jira and Confluence. I hate Atlassian tools so much. The user interfaces are sluggish no matter the hardware you're using... it…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnLinearnone0/10No evidence in the pack mentions data residency, region selection, or storage location controls for Linear workspaces; only unrelated features (access control via Okta, admin app approvals, self-hosting explicitly denied) are covered.
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
- [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”
Jiranone0/10No evidence in the pack addresses data residency, regional hosting options, or data location controls for Jira; the pack only covers features, integrations, and general community sentiment. Missing for 10: documentation of data residency/region selection options, admin controls for choosing storage location, any compliance/residency certification details.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnLinearnone0/10No evidence in the pack addresses AI training data opt-out or any policy preventing customer data from being used to train AI models; the pack covers agents, integrations, API, and workspace features but is silent on AI training data usage policy.
ai-native userControl data retention and deletion
weight 2 · round drawnLinearnone0/10The evidence pack covers admin access control, identity management (Okta/SSO), API rate limits, and agent behavior, but contains no mention of data retention policies, data deletion controls, or configurable retention windows for AI-generated content or session data. Missing for 10: any documentation of retention periods, deletion/export APIs, or admin controls specifically for purging AI agent data or session history.
Jiranone0/10The evidence pack contains no documentation of data retention policies, deletion controls, GDPR/data lifecycle management, or AI-specific data handling controls for Jira; all citations relate to features, integrations, and general community sentiment. Missing for 10: retention policy docs, deletion/export controls, AI training data opt-out or data handling disclosures.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnLinearnone0/10No evidence in the pack addresses telemetry or usage-tracking opt-out settings for Linear; the material covers agents, integrations, API, and product features but nothing about privacy/telemetry controls. Missing for 10: any documentation of a telemetry setting, opt-out toggle, privacy policy statement, or usage-tracking disclosure.
Jiranone0/10No evidence pack item addresses telemetry/usage-tracking opt-out settings for Jira; nothing on privacy controls or data collection toggles is documented. missing for 10: documentation of telemetry collection practices, an opt-out mechanism or setting, and any independent confirmation it works.
Reporting insights — stories about reporting insights in this arenaReporting insights
Stories about reporting insights in this arena
Ai insights
ai-native userAsk AI a question and get an instant answer with citations from my workspace content
weight 2 · round drawnLinearnone0/10The evidence shows Linear Agent can draft updates by gathering context (e.g. 'Write with Agent' reviewing changes and Slack messages) and supports MCP integrations for external AI tools, but there is no documented feature where a user can directly ask a question and receive an instant answer with citations pulled from workspace content. This is a plausible axis for a workspace tool, but no such Q&A/citation feature is evidenced.
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Connect ChatGPT deep research to Linear”
- [claimed-docs] “Previews of Linear issues, views and projects and query Notion AI”
Jiranone0/10The evidence pack mentions Rovo AI connecting data and automating tasks (jira-docs-4, jira-docs-10, jira-docs-15, jira-docs-18), but there is no documentation of a conversational Q&A interface that returns instant answers with citations from workspace content. Missing for 10: any mention of a Rovo AI chat/ask feature, citation of source content in answers, or hands-on evidence of this capability working.
- [claimed-docs] “Rovo AI connects relevant assets and rich data from Confluence, Figma, and your 3rd party apps to your work.”
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
- [claimed-docs] “Use Rovo AI to identify trends to surface new opportunities and remove bottle necks.”
ai-native userHave AI draft a project or initiative status update from recent activity
weight 2 · round to LinearLinear's 'Write with Agent' feature explicitly drafts project status updates by reviewing recent activity changes and linked Slack messages, and Loops can also react to initiative/project changes to keep documents and plans updated automatically. Missing for 10: independent/hands-on corroboration of update quality, and explicit first-party example of initiative-level (vs project-level) status update drafting.
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “You can now edit text with Linear Agent, and use Loops to keep docs and project descriptions up-to-date. Author name indicators let you chec…”
Jira's marketing mentions Rovo AI keeping status 'up to date' via automations and reminders and surfacing trends, which gestures at AI-assisted status tracking, but no evidence shows Rovo actually drafting a written project/initiative status update from recent activity. missing for 10: explicit feature/docs showing AI-generated status update text, independent/hands-on confirmation that this works, and detail on how 'recent activity' is summarized.
- [claimed-docs] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”
- [claimed-docs] “Use Rovo AI to identify trends to surface new opportunities and remove bottle necks.”
Dashboards
product managerBuild dashboards and widgets to report on project progress
weight 2 · round to JiraLinearnone0/10The evidence pack covers Linear's agent/AI coding features, initiatives, teams, and API/webhooks extensively, but contains no mention of dashboard-building or configurable reporting widgets for tracking project progress. Filtered/shared views (linear-docs-13) and project view event subscriptions (linear-docs-61) are the closest hints, but neither describes a dashboard or widget system a PM could assemble for progress reporting.
- [claimed-docs] “You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop.”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
- [community] “The killer missing feature for us is that we can't define different issue types... there's no way to show the issue layout as an expandable …”
Docs confirm multiple progress-tracking views (boards, lists, timeline, calendars) and reporting on cycle time, burndown charts, and company-wide priority visibility, which supports dashboard-style reporting, but no evidence explicitly describes a dedicated dashboard/gadget builder with configurable widgets. missing for 10: explicit documentation of the dashboard/widget-building feature, independent corroboration of dashboard usage for PM reporting.
- [claimed-docs] “Keep work on track whether you're measuring engineering cycle time, burn down charts, or managing capacity.”
- [claimed-docs] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”
- [claimed-docs] “Get visibility on your company's progress towards top priorities as projects advance”
- [claimed-docs] “Teams that integrate Jira Software with Bitbucket release versions 14% more often than those who don't.”
product managerRoll up progress across multiple projects into a single portfolio view
weight 2 · round to JiraLinear's Initiatives feature (grouping multiple projects under a lead team, with status like proposed/canceled and priority) points toward portfolio-style organization, but the evidence never explicitly describes progress roll-up (e.g., aggregated completion percentages or a dedicated portfolio dashboard) across projects. Missing for 10: explicit documentation of progress aggregation/visualization across projects, independent/hands-on confirmation of a portfolio view, and any reporting-specific UI details beyond initiative metadata.
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work and how it contributes to the broad…”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
- [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
- [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
Docs gesture at cross-project visibility ("connect engineering, product, and marketing initiatives" and "visibility on your company's progress towards top priorities") which implies portfolio-level rollup, but there is no explicit mention of a dedicated portfolio/roadmap feature, no detail on how multiple projects are aggregated, and no independent/community evidence confirming this works well in practice. Missing for 10: explicit description of a cross-project portfolio/roadmap feature (e.g. Advanced Roadmaps), concrete UI/workflow detail, and hands-on corroboration from community sources.
- [claimed-docs] “Connect engineering, product, and marketing initiatives to coordinate big launches across every team.”
- [claimed-docs] “Get visibility on your company's progress towards top priorities as projects advance”
- [claimed-docs] “Keep work on track whether you're measuring engineering cycle time, burn down charts, or managing capacity.”
Security — security posture and hardening storiesSecurity
Security posture and hardening stories
Access control
product managerReview an admin audit log of actions taken across the workspace
weight 2 · round drawnLinearnone0/10The evidence pack contains no mention of an admin audit log feature listing actions taken across the workspace; the only near-miss reference (linear-docs-59) discusses private teams enabling 'audits' as a use case, not an actual audit log capability. This is an applicable security/compliance axis for a workspace tool like Linear, but no evidence shows it delivers the capability.
product managerAssign granular permissions and roles to control who can view or edit work
weight 2 · round to LinearLinear offers some access-control building blocks—private/restricted sub-teams and initiatives that limit visibility to team members (linear-docs-15, linear-docs-29, linear-docs-40, linear-docs-59), Okta-based identity and 'existing Linear permissions' management (linear-docs-5, linear-docs-60, linear-docs-67), and admin approval of third-party apps (linear-docs-73)—but there's no evidence of granular, role-based view/edit permission assignment at the issue or field level that a PM could configure themselves. Missing for 10: documented custom roles/permission levels, per-user or per-field view/edit controls, and any PM-facing UI for assigning such permissions beyond team membership.
- [claimed-docs] “Private sub-teams organize groups that work together under one umbrella, like independent business units, skunkworks efforts, or teams handl…”
- [claimed-docs] “For work that requires tighter access, initiatives led by private teams are only visible to team members.”
- [claimed-docs] “Restricted to parent team members — parent team members can see and choose to join the sub-team... Private to team members — the team is hid…”
- [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions.”
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
- [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
- [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
Evidence only mentions SAML/SSO and 'Global and project-level configuration' which loosely implies role/permission scoping, but there's no concrete documentation of granular field-level or issue-level view/edit permission schemes, permission schemes, or roles. Missing for 10: explicit documentation of Jira's permission schemes, project roles, issue security schemes, and independent verification of granular view/edit access control.
- [claimed-docs] “Global and project-level configuration”
- [claimed-docs] “SAML & SSO”
product managerCreate private sub-teams restricted to specific members
weight 1 · round to LinearLinear's docs explicitly describe private sub-teams with restricted visibility options — 'Private to team members — the team is hidden, except to members directly invited to that sub-team' and 'Restricted to parent team members', directly matching the story of PM-created private sub-teams limited to specific members. Additional docs confirm these sub-teams can organize sensitive-data groups and that initiatives led by private teams stay confidential. Missing for 10: independent/hands-on corroboration beyond vendor docs.
- [claimed-docs] “Private sub-teams organize groups that work together under one umbrella, like independent business units, skunkworks efforts, or teams handl…”
- [claimed-docs] “Restricted to parent team members — parent team members can see and choose to join the sub-team... Private to team members — the team is hid…”
- [claimed-docs] “For work that requires tighter access, initiatives led by private teams are only visible to team members.”
- [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
Jiranone0/10No evidence pack items describe private sub-teams or member-restricted groups within Jira; only general permission/SSO mentions exist, none addressing team-level restriction. Missing for 10: documentation on creating restricted sub-teams, member-level access control, or project role/permission scoping evidence.
engineerSecure organization access with SSO and SAML
weight 3 · round to LinearLinear's docs describe Okta-based identity verification and centralized access management for admins, indicating SSO support, and the MCP changelog confirms managing employee access via Okta-managed identity. However, none of the evidence explicitly mentions SAML configuration or enterprise SSO setup details, and there's no independent/hands-on confirmation of the feature working. Missing for 10: explicit SAML protocol documentation, broader SSO provider support beyond Okta, and independent verification of enforcement.
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions.”
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
- [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
- [claimed-docs] “Admins can manage access centrally, without requiring employees to sign in or authorize Linear individually.”
Jira's marketing page explicitly lists "SAML & SSO" as a feature, confirming the capability exists, but there is no detail on implementation, supported IdPs, enforcement, or independent/hands-on confirmation. missing for 10: technical documentation on SAML/SSO setup, supported identity providers, enforcement policies, independent verification of SSO reliability.
- [claimed-docs] “SAML & SSO”
Trust reliability
product managerThe vendor's published uptime SLA and can check real-time incident status via a public status page
weight 3 · round drawnLinearnone0/10No evidence pack item mentions a published uptime SLA or a public status page with real-time incident status; only unrelated docs, community sentiment, and API/agent features are provided. Missing for 10: any mention of an SLA commitment, a status page URL, or incident history/uptime reporting.
product managerThe vendor's documented support response times for each plan tier
weight 2 · round drawnLinearnone0/10No evidence pack item mentions support response time SLAs or plan-tier support commitments; the pack covers product features, API, and agent capabilities but nothing about documented support response times per pricing tier.
Not comparable on these axes
engineerReview AI agent code changes and comment on specific lines from a mobile app, then have the agent iterate
weight 2 · not comparableLinear's docs explicitly state the mobile app supports reviewing code changes, commenting on specific lines, and iterating with Linear Agent (linear-docs-6), backed by broader agent workflow features like Guided Reviews with diff explainers (linear-docs-7), before/after screenshots (linear-docs-27/66), and mobile document editing (linear-docs-71) showing mobile parity investment. Missing for 10: independent/hands-on third-party confirmation of the mobile review-and-iterate flow working smoothly in practice.
- [claimed-docs] “Use the Linear mobile app to review code changes, comment on specific lines, and iterate with Linear Agent.”
- [claimed-docs] “Guided Reviews break diffs into focused sections with explainers on what changed and why.”
- [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation. It also captures before-and-after screenshots”
- [claimed-docs] “It also captures before-and-after screenshots, making visual changes easier to review alongside the code.”
- [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”
Jiran/aJira is an issue-tracking/PM tool, not a code review platform; reviewing AI agent code diffs and commenting on specific lines is a code-review axis (e.g., GitHub/GitLab), not something Jira's product category addresses. No evidence pack item shows Jira offering line-level code diff review from mobile.
engineerRestore an AI coding agent's session to any previous checkpoint in its version history
weight 2 · not comparableLinear explicitly documents checkpoint-based version history restore for coding sessions: "If you need to revert to an earlier version, restore to any previous checkpoint from version history" — this directly matches the story of restoring an AI agent's session state. It's first-party documentation only, with no independent/hands-on corroboration of the restore behavior in practice. Missing for 10: independent/hands-on verification of restore reliability, and detail on granularity/scope of what gets restored.
- [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
- [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
- [claimed-docs] “Coding sessions run in the cloud, so you can prototype ideas and make changes without setting up a local development environment.”
ai-native userHave a coding agent auto-detect and install the toolchains and dependencies it needs for a task
weight 2 · not comparableLinear's docs explicitly state its coding agent detects and installs toolchains/dependencies during a session, plus can pin runtime versions and add setup scripts, and runs in cloud sandboxes without local environment setup. This is direct first-party evidence of the exact capability described, though missing for 10: independent/hands-on verification of this specific auto-detect behavior beyond vendor changelog claims.
- [claimed-docs] “Linear detects and installs the toolchains and dependencies it needs to complete the task.”
- [claimed-docs] “During a session, Linear detects and installs the toolchains and dependencies it needs to complete the task.”
- [claimed-docs] “Teams can go further by pinning runtime versions, adding setup scripts, and defining environment variables.”
- [claimed-docs] “Coding sessions run in the cloud, so you can prototype ideas and make changes without setting up a local development environment.”
ai-native userHave an agent verify its own implementation by navigating the app and capturing before-and-after screenshots
weight 2 · not comparableLinear's own changelog explicitly documents that its coding agent opens the app, navigates a flow, verifies its implementation, and captures before-and-after screenshots for visual review alongside code (linear-docs-27, linear-docs-66, linear-docs-57, linear-docs-25). This directly matches the story's requirement of an agent verifying its own implementation via app navigation and screenshot capture. Missing for 10: independent/hands-on corroboration beyond vendor changelog and no detail on failure/edge-case handling of this verification flow.
- [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation. It also captures before-and-after screenshots”
- [claimed-docs] “It also captures before-and-after screenshots, making visual changes easier to review alongside the code.”
- [claimed-docs] “Once the application is running, Linear Agent tests its work where users experience it: in the browser.”
- [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
- [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation.”
Jiran/aJira is a project/issue-tracking product, not a browser-automation or UI-testing tool; visually verifying implementations via screenshots is outside its product category and not a capability Jira's own app surfaces (unlike browsing/coding agents). No evidence shows Jira itself performing screenshot-based verification, so this axis is a category error for the product type.
engineerHave AI break a code diff into focused sections with explanations of what changed and why
weight 2 · not comparableLinear's 'Guided Reviews' explicitly break diffs into focused sections with explainers on what changed and why, directly matching the story, and this is paired with broader Linear Agent coding-session features (before/after screenshots, mobile review, code review workflows) that support engineers reviewing AI-generated diffs. Missing for 10: independent/hands-on corroboration beyond vendor changelog, and no detail on how granular or customizable the 'sections' are.
- [claimed-docs] “Guided Reviews break diffs into focused sections with explainers on what changed and why.”
- [claimed-docs] “Use the Linear mobile app to review code changes, comment on specific lines, and iterate with Linear Agent.”
- [claimed-docs] “It also captures before-and-after screenshots, making visual changes easier to review alongside the code.”
- [claimed-docs] “Images, fonts, Markdown, and PDFs now render directly inside Linear diffs.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableLinearn/aLinear is a project/issue-tracking and agent-orchestration tool, not a data platform or database with a production/test-data split; 'sandbox vs production data' is a category mismatch for this product type. No evidence suggests Linear offers sandbox environments for testing against non-production data copies.
designerCollaborate visually with my team on a shared whiteboard
weight 2 · not comparableLinearn/aLinear is an issue tracker/project management and AI-agent workflow tool; a shared visual whiteboard for design collaboration is entirely outside its product category and not offered even tangentially in the evidence.
Jiranone0/10The evidence pack contains no mention of a whiteboard or freeform visual-collaboration canvas feature in Jira; it only covers boards/lists/timelines for issue tracking, integrations, and Rovo AI automation. Whiteboarding is a plausible feature for a collaboration suite, but no evidence shows Jira itself ships one.
engineerRequire AI-authored commits to be cryptographically signed with my SSH or GPG key
weight 2 · not comparableLinear's changelog explicitly states coding sessions support signed commits with SSH or GPG keys added in Settings, directly matching the story. missing for 10: no independent/hands-on corroboration confirming enforcement behavior (e.g., that unsigned commits are blocked) or admin-level requirement/policy controls.
- [claimed-docs] “Coding sessions now support signed commits. Add your SSH or GPG key in Settings to enable signing.”