Asana vs Jira

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Asana
   Asana✓fullprobed8/10

   A probe confirms Asana serves a live llms.txt at developers.asana.com/llms.txt with markdown-append instructions for docs pages, directly enabling agent-native doc consumption, and this sits alongside a full REST API reference, OpenAPI spec repo, and API explorer. Missing for 10: independent/community confirmation of agents actually using llms.txt in practice, and a discoverable OpenAPI JSON endpoint (probe found 404s on standard paths, mitigated by the GitHub-hosted spec).

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.asana.com/llms.txt # Asana Docs Documentation > Documentation for Asana Docs Append .md to …”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”

   proof ↗⚑ flag

   Jira—none0/10

   A direct probe found no llms.txt at the expected location (404), and there's no evidence of agent-oriented documentation elsewhere; while an official MCP server exists, that addresses a different story (agent tool connectivity), not llms.txt/agent-docs discoverability.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.atlassian.com/llms.txt”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Asana
   Asana~partialclaimed6/10

   Asana exposes a token-authenticated REST API with webhooks and rule-based automation, enabling scripted/headless interactions suitable for CI-like automation (asana-docs-1, asana-docs-2, asana-docs-15, asana-docs-16, asana-docs-17). However, there is no explicit documentation of CI/CD integration, CLI tooling, or headless execution patterns tailored for automated pipelines. missing for 10: explicit CI/CD examples, dedicated CLI or headless runner, evidence of automated pipeline usage beyond generic API/webhook mentions.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”

   proof ↗⚑ flag

   Jira~partialprobed4/10

   Jira exposes REST APIs (jira-docs-1) and community members confirm using them for automation/scripting (jira-comm-11, jira-comm-16), which supports headless/CI-style usage, but there is no first-party documentation of a CLI, CI/CD pipeline integration, or automation-specific guidance, and probes show no discoverable OpenAPI spec or llms.txt (jira-probe-1, jira-probe-2). missing for 10: official CI/headless automation docs, CLI tool, OpenAPI spec discoverability, and independent confirmation of full CI pipeline usage.

   • [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://…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Asana—none0/10

   Evidence confirms Asana publishes an official MCP server (asana-probe-3), meaning Asana exposes its own tools to other MCP clients — but the story asks the reverse: whether a user can plug external MCP servers into Asana so its AI (e.g., AI Teammates/AI Studio) can consume their tools. No evidence pack item describes Asana's AI agents acting as an MCP client or supporting configuration of external MCP servers as tool sources.

   • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Jira—none0/10

   Evidence only shows Atlassian publishing an official MCP *server* (jira-probe-3), which lets other agents call Jira's tools — the opposite role from this story, which asks whether Jira itself can act as an MCP client and plug in external MCP servers to use their tools. No documentation of Rovo AI or any Jira feature consuming external MCP servers is present. Missing for 10: any evidence of Jira/Rovo AI configuring or connecting to external MCP servers as a client, docs on an MCP client integration, or hands-on confirmation of such usage.

   • [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
   • [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.”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Asana
   Asana✓fullprobed8/10

   Asana documents an official MCP server at a dedicated docs page (asana-probe-3: developers.asana.com/docs/using-asanas-mcp-server), confirming a first-party MCP integration for connecting agents. Missing for 10: independent/hands-on community corroboration of the MCP server working in practice, and more detail on setup/auth scope beyond the docs link.

   • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”

   proof ↗⚑ flag

   Jira✓fullprobed7/10

   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”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Asana—none0/10

   Evidence shows Asana has a REST API, OpenAPI spec, and even an MCP server, but nothing mentions an official CLI tool for interacting with Asana. missing for 10: any documentation of an official Asana CLI, install instructions, or command reference.

   ⚑ flag

   Jira—none0/10

   No evidence of an official Jira CLI anywhere in the pack; evidence covers APIs, integrations, MCP server, and community feedback but nothing about a command-line tool for AI-native workflows.

   ⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Asana
   Asana✓fullclaimed9/10

   Asana publishes a documented REST API with authentication, resource-oriented endpoints, an in-context API explorer, an official OpenAPI spec repo, a developer sandbox, and deprecation/versioning guidance — clearly enabling programmatic/agentic control of the product. Missing for 10: independent third-party hands-on verification of API robustness/reliability beyond vendor docs.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “the API itself will also alert you of upcoming changes. Shortly after we post communication, the API will begin sending Asana-Change headers…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”

   proof ↗⚑ flag

   Jira✓fullprobed7/10

   Jira's REST API and JQL are confirmed both by vendor claims ("Rich APIs") and independent hands-on community usage (writing API wrapper scripts, executing REST queries, valuing JQL), and there is a documented official MCP server enabling agentic access. Missing for 10: a discoverable OpenAPI/llms.txt spec (probes returned 404s) and direct citation of formal API reference docs in this pack.

   • [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.”
   • [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] “Does Plane offer an alternative for JQL (Jira Query Language)? That's what I appreciate most about Jira.”
   • [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
   • [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://…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Asana
   Asana~partialclaimed5/10

   Asana documents token-based API authorization (asana-docs-1) and describes AI Teammates having scoped permissions, identity, and audit trails governed centrally (asana-docs-13), suggesting some notion of least-privilege agent credentials. However, there is no concrete documentation of issuing scoped/limited-permission API tokens or OAuth scopes specifically for third-party agents, nor granular permission configuration UI/API for developer-issued credentials. missing for 10: explicit scoped OAuth/token permission model documentation, developer-facing controls to limit an API credential's access surface, and independent verification that agent credentials can be scoped rather than full-account access.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

   Jira—none0/10

   No evidence of Jira offering scoped or least-privilege API credential issuance (e.g., OAuth scopes, granular API tokens, or agent-specific permission grants); evidence only covers general API/automation/integration features and an MCP server listing, none addressing credential scoping. missing for 10: documentation of scoped/least-privilege API token or OAuth scope creation, agent-specific credential management, and any permission-limiting mechanism for AI agents.

   • [claimed-docs] “Rich APIs”
   • [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack extensively documents Asana's REST API, OpenAPI spec, sandbox, and deprecation policy, but never mentions officially maintained client SDKs (e.g., Python/Node/Java libraries) for developers to build against. Missing for 10: any documentation or reference to first-party SDK packages, language coverage, or SDK versioning/support.

   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.asana.com/openapi.json, https://developers.asana.com/swagger.json, https://develo…”

   proof ↗⚑ flag

   Jira~partialprobed3/10

   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://…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Asana
   Asana✓fullclaimed7/10

   Asana's platform docs explicitly list webhooks alongside rules and API as a core automation mechanism, allowing external systems (including AI agents) to subscribe to Asana events. missing for 10: no dedicated webhook payload/signature-verification docs or independent hands-on confirmation of webhook reliability in the pack.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”

   proof ↗⚑ flag

   Jira—none0/10

   The evidence pack mentions Jira's REST API and automation/integration ecosystem but never documents a webhook subscription mechanism specifically; no docs, community reports, or probes confirm webhook support for AI-native event subscription.

   ⚑ flag

10. ai-native userHand off work between tools or agents without losing context or information

    weight 1 · round to Asana
    Asana~partialprobed6/10

    Asana documents shared memory across AI Teammates so context 'carried forward' between agents, governance/permissions for agent handoff, and cross-tool integration via API, webhooks, app components, and an official MCP server enabling handoff to external agents/tools. However, all of this is vendor-documented with no independent or hands-on verification that context is actually preserved end-to-end across tool/agent handoffs. Missing for 10: independent/hands-on corroboration of lossless handoff, concrete example of an agent-to-agent or tool-to-tool handoff preserving full context, and clarity on how MCP server handles context transfer in practice.

    • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
    • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
    • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”
    • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”
    • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
    • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”

    proof ↗⚑ flag

    Jira~partialprobed5/10

    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…”

    proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Asana
   Asana~partialclaimed6/10

   Asana markets AI Teammates, AI Studio, and 'Asana Dash' as an AI Chief of Staff that surfaces insights and suggestions drawing on Work Graph context and shared memory, which directly matches the story. However, these are vendor claims only—there's no independent/hands-on evidence confirming quality or reliability of these AI-generated insights, and details on how proactive/contextual the suggestions are remain thin. Missing for 10: independent corroboration of AI insight quality, concrete examples of AI-generated suggestions in action, hands-on user reviews of Dash/AI Studio outputs.

   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Jira~partialclaimed5/10

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

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Asana
   Asana✓fullclaimed7/10

   Asana documents rule-based automations, webhooks, and 'AI Studio' for no-code autonomous workflows, plus 'AI Teammates' that run inside workflows with shared memory, scoped permissions, and audit trails — directly supporting background/autonomous automation. Missing for 10: independent/hands-on corroboration that these automations reliably run unattended in production, and more detail on triggers/scheduling beyond marketing copy.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Jira~partialclaimed5/10

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

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Asana
   Asana✓fullclaimed7/10

   Asana ships pre-built AI Teammates/agents (asana-docs-5,6,12,13) and Asana Dash described as an 'AI Chief of Staff' (asana-docs-8) that work within tasks/workflows with shared memory and governance, directly matching delegation of tasks to a built-in assistant. Missing for 10: independent hands-on reviews or third-party validation of AI Teammates actually performing delegated tasks, and detail on the scope/reliability of delegation beyond vendor marketing copy.

   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Jira~partialclaimed6/10

   Jira's Rovo AI is documented as a built-in assistant that can break down big ideas into tasks, auto-assign them, create automations, and surface trends, which matches the delegate-to-AI-assistant story, but all evidence is vendor marketing copy with no independent or hands-on confirmation of how well this delegation actually works. missing for 10: independent/hands-on verification of Rovo AI task delegation, community feedback specifically on Rovo AI's reliability, and detail on scope/limits of delegated actions.

   • [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.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Asana
   Asana~partialprobed6/10

   Asana ships AI Teammates/AI Studio and a Chief-of-Staff style agent (Dash) described as operating with shared memory and governance, plus an MCP server enabling natural-language agent interaction, suggesting real natural-language control surfaces exist. However, there is no first-party documentation or hands-on evidence showing an end user issuing free-form natural-language commands directly in the core Asana UI to create/manage tasks; most 'AI-native' evidence is marketing copy without demonstrated workflows. missing for 10: hands-on demonstration or detailed docs of natural-language command execution in the main product UI, independent verification of Dash/AI Teammates handling arbitrary NL requests, and clarity on how MCP server maps to end-user NL commands versus developer/agent use.

   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”
   • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”

   proof ↗⚑ flag

   Jira~partialprobed5/10

   Jira ships Rovo AI features (automations, task breakdown, trend surfacing) framed as AI-assist, and Atlassian publishes an official MCP server enabling AI agents to operate Jira via natural-language tool calls. However, there's no first-party documentation of a native natural-language command interface inside Jira itself, and no independent/hands-on evidence confirming reliability of either the MCP server or Rovo AI's language-driven control. missing for 10: direct docs on natural-language chat/command interface in Jira UI, independent verification of MCP server or Rovo AI command accuracy.

   • [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”

   proof ↗⚑ flag

5. ai-native userBuild and configure my own custom AI agent within the product

   weight 2 · round to Asana
   Asana~partialclaimed6/10

   Asana markets 'AI Studio' for no-code agent automations and 'custom AI Teammates' built from team expertise, with governance and shared memory features (asana-docs-6,7,12,13), indicating a self-service agent-building capability. However, all evidence is first-party marketing copy with no tutorial, screenshots, or independent hands-on account of actually configuring an agent end-to-end. missing for 10: independent/hands-on verification of building a custom agent, detailed step-by-step configuration docs, community confirmation of the feature working as advertised.

   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Jira—none0/10

   Evidence shows Jira's Rovo AI provides pre-built AI-assist features (automations, task breakdown, trend detection) but no documentation of a builder/studio letting users create and configure their own custom AI agents. Missing for 10: any mention of an agent-builder UI, agent configuration options, or custom agent deployment within 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.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Asana
   Asana✓fullclaimed8/10

   Asana's developer docs explicitly state each API endpoint has a built-in, in-context API explorer for making requests and viewing responses (asana-docs-16), backed by a RESTful reference (asana-docs-15) and an official OpenAPI spec repo (asana-supp-openapi-spec, asana-docs-20), plus a developer sandbox for safe testing (asana-docs-17). Missing for 10: independent/hands-on confirmation of the explorer's runnable examples in practice, and a working public openapi.json endpoint (probe found 404s at standard paths).

   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”

   proof ↗⚑ flag

   Jira—none0/10

   No evidence pack item shows an interactive, runnable-example API reference for Jira; the closest technical evidence is generic 'Rich APIs' marketing copy and mentions of REST/JQL usage from developers, with no docs or hands-on account of a try-it console. Probes explicitly found no llms.txt or openapi.json at the developer site, further indicating no discoverable interactive API spec was surfaced.

   • [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.”
   • [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://…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Asana
   Asana✓fullprobed9/10

   Asana publishes an official OpenAPI specification (asana_oas.yaml plus app-components spec) in the Asana/openapi GitHub repo, which is machine-readable and downloadable, and the REST API docs corroborate a resource-oriented JSON API with in-context explorer built from this spec. Missing for 10: a directly hosted openapi.json/swagger.json endpoint on developers.asana.com (probe found 404s at expected discovery URLs), so users must know to fetch it from GitHub rather than a standard API-discovery path.

   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.asana.com/openapi.json, https://developers.asana.com/swagger.json, https://develo…”

   proof ↗⚑ flag

   Jira—none0/10

   No evidence of a downloadable OpenAPI/Swagger spec; probes explicitly show 404s for candidate OpenAPI endpoints at developer.atlassian.com and no llms.txt. Community praise for REST/JQL access doesn't equate to a machine-readable spec being published.

   • [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.”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Asana
   Asana✓fullclaimed8/10

   Asana explicitly documents a developer sandbox — a temporary Asana domain with limited users — for testing purposes, plus feature-flag headers to test upcoming API behavior before it goes live, directly supporting isolated testing without touching production data. missing for 10: independent/hands-on confirmation of sandbox fidelity and any limits (e.g., data reset, scale) that might affect real-world AI-agent testing workflows.

   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “you can test out how the API will behave by sending additional headers in your requests. Sending an Asana-Enable header including comma-sepa…”
   • [claimed-docs] “Docs, "Deprecations" ("this page describes our deprecation process"): "We will provide a clear description of the change, how it affects you…”

   proof ↗⚑ flag

   Jira—none0/10

   No evidence pack mentions a sandbox, test instance, staging environment, or non-production data isolation feature for Jira; all evidence covers general features, integrations, and community sentiment unrelated to sandbox testing. Missing for 10: any documentation of a Jira sandbox/staging environment, data isolation mechanism, or test-instance provisioning for AI-native testing.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Asana
   Asana✓fullclaimed8/10

   Asana documents a formal deprecation process with Asana-Change headers, Asana-Enable headers for opt-in testing, migration plans, and a deprecation period, plus a public OpenAPI spec repo and REST reference with an interactive explorer, indicating a mature versioned/documented API lifecycle. Missing for 10: independent third-party corroboration of deprecation policy adherence over time and explicit API version numbering scheme details.

   • [claimed-docs] “the API itself will also alert you of upcoming changes. Shortly after we post communication, the API will begin sending Asana-Change headers…”
   • [claimed-docs] “you can test out how the API will behave by sending additional headers in your requests. Sending an Asana-Enable header including comma-sepa…”
   • [claimed-docs] “Docs, "Deprecations" ("this page describes our deprecation process"): "We will provide a clear description of the change, how it affects you…”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”

   proof ↗⚑ flag

   Jira—none0/10

   Evidence confirms Jira exposes REST APIs (jira-comm-16, jira-docs-1) but there is no documentation of API versioning scheme or a deprecation policy; probes for OpenAPI specs and llms.txt both 404, suggesting no discoverable machine-readable API contract. Missing for 10: documented API versioning scheme, explicit deprecation/sunset policy, changelog 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.”
   • [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://…”

   proof ↗⚑ flag

5. ai-native userThe documented API rate limits and concurrency caps before building automation at scale

   weight 2 · round drawn
   Asana—none0/10

   The evidence pack covers Asana's REST API, OpenAPI spec, deprecation policy, and developer sandbox, but nothing addresses documented rate limits or concurrency caps for API usage. Since no citation speaks to this specific axis, it cannot be credited even though it's a fair question for an API platform.

   ⚑ flag

   Jira—none0/10

   No evidence pack item documents specific API rate limits, concurrency caps, or throttling thresholds for Jira's REST/API platform; probes for OpenAPI specs and llms.txt returned 404s, and no developer docs on rate limiting are cited. missing for 10: documented rate-limit numbers/headers, concurrency cap docs, throttling/backoff guidance.

   • [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://…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Jira
   Asana—none0/10

   The evidence describes single-task creation via the API, rule-based automation, webhooks, and AI Studio workflows, but nowhere mentions a bulk/batch endpoint or the ability to update many items in one call as an AI-native user. Missing for 10: explicit bulk/batch API operations, multi-item update endpoints, or documented bulk action support.

   ⚑ flag

   Jira~partialprobed6/10

   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://…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Asana
   Asana✓fullclaimed7/10

   Asana's native Rules engine plus 'rule actions, webhooks, and API' explicitly supports trigger-based automation on events, and AI Studio adds no-code automations layered on top, with app components allowing custom logic to plug into rules. Missing for 10: independent hands-on verification of AI-native rule-building via API/agent, and detail on the range of triggerable events/conditions.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”

   proof ↗⚑ flag

   Jira✓fullclaimed6/10

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Asana~partialclaimed4/10

   Asana's platform docs show general automation via rules, webhooks, API, and AI Studio's no-code automations, which could support recurring workflows, but no evidence explicitly describes scheduling or recurring job triggers (e.g., time-based rule triggers). Missing for 10: explicit documentation of recurring/scheduled triggers, cron-like automation, or examples of automating tasks on a recurring schedule.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”

   proof ↗⚑ flag

   Jira~partialclaimed4/10

   Jira's docs mention Rovo AI-driven automations for reminders and workflow rules (jira-docs-4) and general workflow automation (jira-intdir-1, jira-docs-13), implying some scheduling-like capability, but no evidence explicitly describes recurring/scheduled job triggers or cron-like automation configuration. Missing for 10: explicit documentation of scheduled/recurring automation triggers, independent confirmation of recurring job scheduling, and API/automation examples showing time-based recurrence.

   • [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.”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Asana—none0/10

   No evidence of version history, review workflows, or rollback capability for Asana rules/automations or AI Studio workflows; docs cover API deprecation headers and app components, not automation versioning/rollback. missing for 10: version history UI for rules/automations, diff/review workflow before publishing changes, rollback/restore to prior automation version.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Docs, "Deprecations" ("this page describes our deprecation process"): "We will provide a clear description of the change, how it affects you…”

   proof ↗⚑ flag

   Jira—none0/10

   Evidence mentions Jira automation features (Rovo AI rules, custom workflows) but nothing about versioning automation rules, reviewing change history, or rolling back automation configurations. No changelog, version control, or rollback capability for automations is documented anywhere in the pack. missing for 10: version history for automation rules, review/diff of automation changes, rollback mechanism, any documentation or community mention of these capabilities.

   ⚑ flag

Ai task automation

1. ai-native userHave AI automatically triage and prioritize incoming bugs and tasks

   weight 2 · round to Asana
   Asana~partialclaimed5/10

   Asana offers rule-based automation, webhooks/API, AI Studio no-code automations, and AI Teammates described as handling 'complex, coordination-heavy work' with shared memory and governance — these are generic building blocks that could be configured to triage/prioritize tasks, but no evidence explicitly documents a bug-triage or prioritization use case or template. Missing for 10: a concrete documented workflow or template showing AI classifying/prioritizing incoming bugs or tasks, independent/hands-on validation of such a workflow.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Jira~partialclaimed4/10

   Jira markets Rovo AI for breaking down tasks and auto-assigning to the right person, identifying trends/bottlenecks, and creating automations, which are adjacent to triage/prioritization, but there is no explicit documentation of an AI feature that specifically triages or prioritizes incoming bugs/tasks. missing for 10: explicit bug/task triage-and-prioritization AI feature docs, independent/hands-on confirmation that Rovo AI performs this triage reliably.

   • [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] “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] “Prioritize high-impact work, break down big projects into clear tasks, and cultivate ownership.”

   proof ↗⚑ flag

2. ai-native userHave my in-app AI assistant learn my tone, shorthand, and preferences to tailor its output

   weight 1 · round to Asana
   Asana~partialclaimed4/10

   Asana's AI Teammates feature claims 'shared memory' where 'every piece of feedback, every preference gets carried forward,' which loosely maps to personalization, but there's no specific evidence of learning tone, shorthand, or writing style, nor any hands-on validation of this personalization actually working. missing for 10: evidence of tone/style/shorthand learning specifically, first-party detail on how preference adaptation works mechanically, and independent corroboration that AI output actually reflects user's individual style.

   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”

   proof ↗⚑ flag

   Jira—none0/10

   No evidence describes Rovo AI or any Jira AI feature learning a user's tone, shorthand, or personal preferences to tailor output — the AI mentions focus on automations, summarization, and integrations, not personalization/persona-learning. missing for 10: any documentation of tone/style learning, personalization memory, or adaptive output based on user preferences.

   • [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.”

   proof ↗⚑ flag

Workflow automation

1. engineerAuto-generate a changelog for each release so shipping progress is easy to review

   weight 1 · round drawn
   Asana—none0/10

   Asana is a project/task management tool, not a code repository or CI/CD system; nothing in the evidence shows any feature for generating release changelogs from commits, PRs, or version tags. While Asana has APIs, rules, and automation features, none are documented as producing changelogs tied to releases.

   ⚑ flag

   Jira—none0/10

   No evidence in the pack mentions release notes or changelog generation features in Jira; only generic mentions of Bitbucket integration and release version tracking without changelog automation specifics. Missing for 10: any documentation of automated changelog/release notes generation tied to versions or releases, evidence of the feature's actual usage or third-party corroboration.

   ⚑ flag

2. product managerBuild multi-step automations without writing code

   weight 2 · round to Jira
   Asana~partialclaimed6/10

   Asana explicitly markets 'AI Studio – Powerful no-code automations' and references 'rule actions' as part of its automation platform, directly supporting a PM building multi-step automations without code. However, the evidence pack lacks deeper documentation (e.g., a rules builder walkthrough, examples of multi-step conditional logic, or independent hands-on validation) beyond marketing taglines. missing for 10: detailed no-code rule-builder documentation/tutorial, independent user validation of multi-step automation building.

   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”

   proof ↗⚑ flag

   Jira✓fullclaimed6/10

   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”

   proof ↗⚑ flag

3. engineerBuild trigger-and-action automation rules to eliminate repetitive manual steps

   weight 3 · round drawn
   Asana~partialclaimed6/10

   Evidence confirms Asana has a rule-based automation surface ("rule actions", app components built on the surface of "rules", and AI Studio's no-code automations) that lets engineers/users automate repetitive steps, and the API/webhooks can be combined with rules for custom triggers. However, the pack lacks first-party documentation detailing the actual trigger types, conditions, or multi-step rule builder UI, so the story is only partially evidenced. Missing for 10: dedicated Rules-builder documentation showing trigger/condition/action configuration, and independent/hands-on confirmation of building such rules.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”

   proof ↗⚑ flag

   Jira~partialclaimed6/10

   Jira's docs explicitly describe automation that 'connects tools to any Jira workflow' and lets users build custom rules (including AI-assisted reminders and work-forwarding rules), matching the trigger-and-action automation story. However, all evidence is vendor marketing copy with no independent/hands-on confirmation of the automation rule builder's reliability or ease of use, and community comments focus on other pain points rather than corroborating automation specifically. Missing for 10: independent/hands-on evidence of building automation rules, detail on trigger/condition/action rule builder UI, and evidence of scale/reliability of automation execution.

   • [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.”
   • [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] “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.”

   proof ↗⚑ flag

4. engineerCreate a workflow that runs on a schedule or recurring event to handle routine team work

   weight 2 · round drawn
   Asana~partialclaimed4/10

   Asana's docs reference rule-based automation ('rule actions, webhooks, and our API') and AI Studio's 'no-code automations,' suggesting engineers can build workflow automations, but no evidence explicitly documents a schedule/time-based or recurring-event trigger mechanism for these workflows. Missing for 10: explicit documentation of scheduled/cron-like or recurring-event triggers in Rules or AI Studio, and any hands-on/independent confirmation that such scheduled automations work reliably.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”

   proof ↗⚑ flag

   Jira~partialclaimed4/10

   Jira's marketing pages repeatedly mention 'automation' and 'customizable workflows' connecting tools and keeping status up to date (jira-docs-13, jira-docs-22, jira-intdir-1, jira-docs-4), which implies rule-based automation exists, but none of the evidence explicitly describes scheduled/recurring time-based triggers for routine work. Community evidence focuses on UI complaints, not automation scheduling. missing for 10: explicit documentation of a schedule/cron-style trigger in Jira Automation, independent/hands-on confirmation that scheduled automations work reliably.

   • [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.”
   • [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] “Use Rovo AI to create custom automations to keep your status up to date - from automated reminders to rules that move work forward.”

   proof ↗⚑ flag

5. 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 drawn
   Asana—none0/10

   No evidence describes rate limits, throttling behavior, overage charges, or hard stops for exceeding automation/API quotas; docs cover deprecations, sandbox, and API basics but not usage limits or their consequences.

   ⚑ flag

   Jira—none0/10

   No evidence pack items document rate limit thresholds, overage charges, throttling behavior, or hard stops for Jira's automation or API usage; the pack only covers general features, integrations, and unrelated community complaints/praise.

   ⚑ flag

Cross tool sync

1. designerKeep project status updated from my design tool without switching apps

   weight 2 · round to Jira
   Asana~partialclaimed3/10

   Asana's API, webhooks, and App Directory (asana-docs-2, asana-docs-11) allow third-party apps to create/update tasks and status without leaving another tool, and app components let external apps surface inside the Asana UI (asana-docs-3/10/14), which is the general mechanism such a design-tool integration would use. However, there is no evidence of an actual Figma/Sketch/Adobe-type design tool integration or of status updates flowing specifically from a design tool into Asana project status. missing for 10: a named design-tool integration (e.g., Figma plugin) syncing project status, and any hands-on/community confirmation it works.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”

   proof ↗⚑ flag

   Jira~partialcommunity4/10

   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…”

   proof ↗⚑ flag

Docs knowledge

1. product managerCreate and organize shared docs and notes alongside my project work

   weight 3 · round to Jira
   Asana—none0/10

   No evidence in the pack shows a native Asana docs/notes feature for organizing shared documentation alongside project work; the docs and community items focus on tasks, API/dev platform, and AI Teammates, not a wiki/notes capability. One community comment even suggests a competing tool being compared lacks 'free form notes and wiki' relative to Asana/Trello, but nothing confirms Asana itself ships a shared-doc feature.

   • [community] “This seems to just be the boards and task lists without the free form notes and wiki? It pretty clearly replaces Trello and Asana.”

   proof ↗⚑ flag

   Jira~partialclaimed4/10

   Jira itself is an issue tracker without native document/notes authoring; evidence shows this capability is delivered only via integration with a separate product, Confluence (jira-docs-24), not within Jira's own UI. This is a real workaround requiring another tool rather than native support. Missing for 10: evidence of native doc/notes creation inside Jira, first-party docs describing an in-product wiki/notes feature, and independent confirmation that PMs can organize docs alongside issues without leaving Jira.

   • [claimed-docs] “76% of Jira Software customers said they shipped projects faster after adding Confluence to help organize and manage agile projects.”

   proof ↗⚑ flag

In context discussion

1. engineerComment directly on specific text or images within an item's description

   weight 2 · round drawn
   Asana—none0/10

   The evidence pack contains only API/developer platform docs and general community sentiment; nothing describes inline commenting on specific text or images within a task/item description. Missing for 10: any documentation or hands-on evidence of annotation/inline commenting features on description text or embedded images.

   ⚑ flag

   Jira—none0/10

   No evidence pack item describes inline commenting on specific text or images within an item's description; only general feature marketing and unrelated community complaints are present. Missing for 10: any documentation or hands-on evidence of anchored/inline annotation comments on description text or images.

   ⚑ flag

Real time sync

1. engineerSee teammates' changes reflected instantly across open sessions without refreshing

   weight 3 · round drawn
   Asana—none0/10

   The evidence pack contains no mention of real-time UI sync, live presence, or websocket-based updates in Asana's interface — only API/webhook automation, developer sandbox, and AI Teammate features, none of which address instant cross-session UI updates for engineers viewing shared work.

   ⚑ flag

   Jira—none0/10

   No evidence describes real-time/live sync of updates across open sessions without refresh; docs focus on integrations, AI-assist, and workflow customization, and community comments even mention slow loading/reload loops rather than instant live updates.

   ⚑ flag

Team chat

1. engineerChat with my team directly inside the same tool I plan work in

   weight 2 · round drawn
   Asana—none0/10

   Asana's evidence pack covers task management, APIs, automations, and AI teammates, but nothing documents an in-app real-time chat/messaging feature for team communication; the closest mention (asana-comm-5) is a vague anecdote about using task comments instead of Slack, not a documented chat capability.

   • [community] “Asana has been around awhile and my team always used it for remote team communication and project management. We never saw the need for apps…”

   proof ↗⚑ flag

   Jira—none0/10

   Evidence shows Jira integrates with Slack for notifications/automation (e.g., jira-intdir-1, jira-docs-2) but there is no documented built-in chat feature for real-time team conversation inside Jira itself; comments on tickets are asynchronous, not chat.

   ⚑ flag

Visual collaboration

1. designerCollaborate visually with my team on a shared whiteboard

   weight 2 · round drawn
   Asana—none0/10

   No evidence in the pack of any whiteboard or visual collaboration canvas feature in Asana; documentation only covers API, automation, AI teammates, and app components. Missing for 10: any whiteboard/canvas feature, real-time visual co-editing, design collaboration tools.

   ⚑ flag

   Jira—none0/10

   No evidence pack item mentions a whiteboard or visual collaboration canvas feature within Jira itself; Jira is a work-tracking tool and while a whiteboard could plausibly be part of an Atlassian suite (Confluence has one), none of the evidence shows Jira offering this capability.

   ⚑ flag

App ecosystem

1. engineerKeep tasks bi-directionally synced with my code repository's issue tracker instead of duplicating data

   weight 2 · round to Jira
   Asana—none0/10

   The evidence only shows generic Asana API/webhook/app-directory capabilities (e.g., asana-docs-2, asana-docs-11) that could be used to build custom sync, but there is no documentation of a specific, ready-made bi-directional sync with a code repository issue tracker (e.g., GitHub/GitLab/Jira issues) that avoids data duplication. Without a named integration or sync workflow for this exact use case, this remains unevidenced.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

   Jira~partialclaimed5/10

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

   proof ↗⚑ flag

2. engineerSee my assigned tasks from multiple project management tools in one unified view

   weight 2 · round drawn
   Asana—none0/10

   Evidence shows Asana's API/integrations let other apps create Asana tasks or embed components, but there is no evidence of a unified view that aggregates an engineer's assigned tasks from multiple different project-management tools (e.g., Jira, Trello) inside Asana itself. Missing for 10: any documentation of a cross-tool task aggregation/unified inbox feature, evidence of pulling in tasks from other PM tools, or a 'My Tasks' view spanning external systems.

   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”

   proof ↗⚑ flag

   Jira—none0/10

   Evidence 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”

   proof ↗⚑ flag

3. engineerConnect common tools like Slack, GitHub, and Google Drive natively

   weight 2 · round to Jira
   Asana~partialclaimed4/10

   Asana's docs mention a broader integration ecosystem (App Directory apps, app components that 'plug directly into Asana UI', APIs/webhooks for building integrations), implying that tools can connect natively, but no evidence explicitly names Slack, GitHub, or Google Drive as first-party native integrations. Missing for 10: explicit documentation of native Slack/GitHub/Google Drive connectors, hands-on confirmation of their functionality, and any independent corroboration of these specific integrations working out-of-the-box.

   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”

   proof ↗⚑ flag

   Jira~partialclaimed6/10

   Jira's marketing pages explicitly mention native integrations with Slack (jira-intdir-1) and a marketplace of 3000+ apps including many common tools, plus Bitbucket/GitHub-adjacent dev tooling and Trello sync, but GitHub and Google Drive are never explicitly named as native integrations—only implied via generic '3rd party apps' and marketplace claims. Community evidence is silent on these specific integrations, so there's no independent corroboration of the exact tool list named in the story. missing for 10: explicit first-party or independent confirmation of native GitHub and Google Drive connectors, and hands-on validation of Slack/GitHub/Drive integration quality.

   • [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] “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] “Keep work up-to-date by tracking progress from your favorite tools like Slack, Figma and Gmail powered by an AI-assist”

   proof ↗⚑ flag

4. product managerConnect my workspace to thousands of third-party tools via an app marketplace

   weight 2 · round to Jira
   Asana~partialclaimed6/10

   Asana docs confirm an 'App Directory' with many third-party apps that create tasks and kick off workflows, plus a public REST API, webhooks, and app components for building custom integrations, which together support a marketplace-style ecosystem. However, no evidence quantifies the marketplace size ('thousands of tools') or shows a browsable marketplace UI/listing, and no independent/community source corroborates breadth of integrations. missing for 10: concrete count/scale of App Directory listings, independent hands-on evidence of marketplace breadth, and marketplace browsing/install UX documentation.

   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

   Jira✓fullcommunity8/10

   Jira's own marketing docs explicitly claim 3000+ integrations via the Atlassian Marketplace, plus named examples (Slack, Figma, Gmail, Bitbucket, Trello, Tempo, Zephyr) and REST API access corroborated by community users who build scripts against it. Missing for 10: independent marketplace-scale verification and hands-on product-manager account of app installation flow.

   • [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] “Collaborate across tools with transparency and create workflows that work for you by syncing Trello and Jira Software.”
   • [claimed-docs] “Teams that integrate Jira Software with Bitbucket release versions 14% more often than those who don't.”
   • [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.”

   proof ↗⚑ flag

Extensibility

1. designerBuild custom views and dashboard widgets that feel native to the product

   weight 1 · round to Asana
   Asana~partialclaimed5/10

   Asana's developer docs describe 'app components' that let third-party apps plug directly into the Asana UI on the surface of tasks or rules, which supports building native-feeling integrations, but the story's specific asks—custom views and dashboard widgets—are not evidenced; only task/rule surface extensions are documented, with no dedicated widget/dashboard SDK or design guidelines mentioned. Missing for 10: explicit dashboard widget support, custom view builder APIs, design system/UI kit guidance, and independent/hands-on confirmation from designers building such components.

   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”

   proof ↗⚑ flag

   Jira—none0/10

   Evidence 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”

   proof ↗⚑ flag

Getting started

1. product managerThat exporting my workspace preserves full history—comments, attachments, and audit trails—not just task titles

   weight 3 · round drawn
   Asana—none0/10

   No evidence pack item addresses workspace export functionality, let alone preservation of comments, attachments, or audit trails during export; docs focus on API, automation, and AI Teammates instead.

   ⚑ flag

   Jira—none0/10

   No evidence in the pack addresses export functionality, data portability, or preservation of comments/attachments/audit trails during export—only feature marketing on tracking, automations, and integrations. Missing for 10: any documentation of export/backup functionality, evidence that comments/attachments/history are retained on export, and independent confirmation of export fidelity.

   ⚑ flag

2. engineerFollow a guided walkthrough to set up my workspace the first time

   weight 1 · round drawn
   Asana—none0/10

   The evidence pack covers Asana's developer API, OpenAPI specs, MCP server, and general community sentiment about product quality, but contains no mention of a guided onboarding walkthrough or setup wizard for new workspace users. Missing for 10: any documentation of an in-app guided setup flow, first-run wizard, or onboarding checklist for engineers configuring a new Asana workspace.

   ⚑ flag

   Jira—none0/10

   No evidence of a guided onboarding walkthrough for first-time workspace setup; evidence covers features, integrations, and community complaints about confusing UX/complexity but nothing about an onboarding flow or setup wizard. missing for 10: guided setup wizard/tour documentation, first-run onboarding experience, evidence of onboarding checklist or tutorial.

   ⚑ flag

3. product managerImport my data from another tool when switching over

   weight 2 · round drawn
   Asana—none0/10

   No evidence describes an import/migration feature for bringing data from other tools (e.g., CSV import, Trello/Jira migration wizards); the pack only covers API access, app directory integrations, and AI teammates, none of which constitute a documented data-import capability for onboarding.

   ⚑ flag

   Jira—none0/10

   No evidence pack items mention data import/migration tools, CSV import, or migration assistants from other tools (e.g., Trello, Asana, Monday) into Jira; evidence only covers integrations, APIs, and general Jira features/complaints, none addressing onboarding/import specifically.

   ⚑ flag

4. product managerJumpstart a new project using pre-built templates

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack contains no mention of Asana's project templates or template galleries for jumpstarting new projects; all docs entries focus on API, integrations, and AI Teammates. missing for 10: any documentation or community evidence of pre-built project templates, template gallery, or template creation workflow.

   ⚑ flag

   Jira✓fullclaimed7/10

   Jira's official feature page explicitly states pre-built and customizable templates for any project type, from agile sprints to marketing campaigns, directly matching the PM onboarding story. Missing for 10: independent/hands-on corroboration of the template gallery experience and detail on breadth/quality of specific templates beyond the marketing claim.

   • [claimed-docs] “Start fast with pre-built and customizable templates for any project, from agile sprints to marketing campaigns.”

   proof ↗⚑ flag

Pricing transparency

1. product managerWhether my plan enforces a minimum seat count or annual billing commitment before I subscribe

   weight 3 · round drawn
   Asana—none0/10

   No evidence in the pack addresses Asana's pricing plans, minimum seat requirements, or annual billing commitments; all evidence concerns API/developer docs and general community sentiment.

   ⚑ flag

   Jira—none0/10

   No evidence in the pack addresses pricing terms, seat minimums, or annual billing commitments for Jira plans; all citations concern product features, integrations, or general community sentiment.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Asana
   Asana~partialclaimed6/10

   Asana's REST API is comprehensive and well-documented (CRUD on tasks, projects, webhooks, app components, OpenAPI spec, sandbox, explorer), covering most core workflow actions available in the UI. However there's no evidence that newer AI-native surfaces (AI Studio, AI Teammates/Dash) or all UI-specific features are fully exposed via the same API, so full UI/API parity isn't demonstrated. missing for 10: explicit confirmation that AI Studio/Teammates features and all UI settings/admin controls are API-accessible, independent verification of full parity.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”

   proof ↗⚑ flag

   Jira~partialprobed4/10

   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://…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Asana
   Asana~partialclaimed4/10

   Asana's REST API returns JSON, an open format, so data could in principle be pulled out via API calls (asana-docs-15), and OpenAPI specs are published for structured access (asana-supp-openapi-spec). However, there is no documented dedicated bulk-export/full-account-export feature, no CSV/backup tool, and no explicit data-portability policy in the evidence pack. Missing for 10: a documented full-data export/backup mechanism, guarantees of completeness, and independent confirmation that users can fully migrate away using this API.

   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”

   proof ↗⚑ flag

   Jira—none0/10

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

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Asana—none0/10

   Asana is a closed, proprietary SaaS product; the only public repo referenced (Asana/openapi) contains API specification files, not the product's actual source code, and no evidence indicates any open-license release of Asana's codebase.

   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”

   proof ↗⚑ flag

   Jira—none0/10

   Jira is closed-source, proprietary SaaS; no evidence of any open-licensed source availability. The axis applies (a buyer could ask whether a product's source is open), but nothing in the evidence pack indicates open licensing—only feature marketing, API/integration mentions, and community commentary.

   ⚑ flag

Mobile access

1. engineerManage my tasks from a full-featured native mobile app without missing desktop functionality

   weight 2 · round drawn
   Asana—none0/10

   The evidence pack contains no mentions of a native mobile app, mobile feature parity, or any mobile-specific capability—only API, developer platform, AI features, and general community sentiment about the web app's performance. Absence of evidence for this applicable axis (mobile apps are a plausible feature for a task/project management SaaS) means 'none'.

   ⚑ flag

   Jira—none0/10

   No evidence in the pack mentions a native mobile app, its feature parity with desktop, or mobile usability at all; all citations focus on web features, integrations, and general UI complaints. missing for 10: any mention of a native mobile app, mobile feature parity, offline mobile support, or mobile-specific user feedback.

   ⚑ flag

Task management

1. product managerTrack cross-team dependencies to coordinate large launches

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack contains no mention of Asana's dependency-tracking, portfolios, or cross-team coordination features (e.g., task dependencies, portfolio views) that would support this story; documentation cited focuses on API access, integrations, and AI Teammates rather than planning/tracking capabilities like dependency management.

   ⚑ flag

   Jira~partialcommunity6/10

   Docs explicitly claim cross-team dependency tracking for launches (connecting engineering, product, marketing; timeline/board views; progress visibility on priorities), which directly supports the story. However, there's no dedicated dependency-linking feature (e.g., blocking/blocked-by cross-project links) documented, and community feedback raises usability/reliability concerns (slow, buggy, confusing workflows) that could undermine coordination at scale. Missing for 10: explicit documentation of dependency-linking mechanics across teams/projects, independent case studies of large launch coordination, and confirmation these features work smoothly in practice.

   • [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] “Keep work on track whether you're measuring engineering cycle time, burn down charts, or managing capacity.”
   • [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…”

   proof ↗⚑ flag

2. product managerCustomize fields and workflow statuses to match my team's process

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack contains only API/developer-platform docs, AI teammate features, and community sentiment about UI/performance — none of it addresses custom fields or configurable workflow statuses, which is the actual subject of this story. Although this is a fair and expected capability for a work-management product like Asana, no evidence in the pack demonstrates it.

   ⚑ flag

   Jira~partialcommunity7/10

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

   proof ↗⚑ flag

3. product managerTrack initiatives with status, priority, and an owning team

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack contains no mention of Asana's Portfolios/Goals features, custom fields for status or priority, or team ownership assignment for initiatives — it is entirely focused on the developer API, AI Teammates/agents, and general community sentiment. Without evidence of initiative-level tracking with status, priority, and owning team, this capability cannot be credited.

   ⚑ flag

   Jira✓fullcommunity7/10

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

   proof ↗⚑ flag

4. engineerPlan and manage sprints for agile software development

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack contains no mention of sprint boards, backlogs, story points, or agile/scrum-specific features in Asana; it focuses on API/developer platform capabilities and AI agent features. Community comments only compare Asana's general UI to Jira without confirming sprint-planning functionality, and some users note Asana lacks features that PMs/engineers need versus Jira for dev workflows.

   • [community] “I've found Asana to be a much, much nicer product to work with than Jira (at least as a developer, not sure about from the management side.)…”
   • [community] “While better than Jira in UI, I haven't been able to like Asana as a product for some reason. In my previous company we moved away from Asan…”
   • [community] “i remember reading about asana on here years ago. wasn't it supposed to be the thing that saved us from JIRA but ended up turning into the v…”

   proof ↗⚑ flag

   Jira~partialcommunity7/10

   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…”

   proof ↗⚑ flag

5. engineerCreate tasks and assign them to teammates with due dates

   weight 3 · round to Jira
   Asana~partialclaimed5/10

   Docs confirm Asana supports creating tasks via UI/API (asana-docs-1, asana-docs-11, asana-docs-15) and that third-party apps can create tasks and kick off workflows, but the evidence pack never explicitly documents the assignee or due-date fields on a task object. Missing for 10: explicit documentation of assignee and due-date task fields, and independent hands-on confirmation of assigning tasks with due dates.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

   Jira✓fullcommunity7/10

   Jira's core issue-tracking evidence confirms creating tasks and assigning them to individual teammates (jira-docs-10, jira-docs-23) and community evidence corroborates real-world use of ticket assignment workflows (jira-comm-2, jira-comm-7). Customizable fields (jira-docs-3) imply due-date support but the pack never explicitly documents a due-date field. Missing for 10: explicit documentation/screenshot of a due-date field on task creation, independent hands-on confirmation of due-date + assignment working together.

   • [claimed-docs] “Breakdown big ideas into actionable tasks and automatically assign them to the right person with Rovo AI.”
   • [claimed-docs] “Prioritize high-impact work, break down big projects into clear tasks, and cultivate ownership.”
   • [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…”

   proof ↗⚑ flag

6. engineerBreak work into subtasks and link dependent tasks so blocking order is clear

   weight 3 · round to Jira
   Asana—none0/10

   The evidence pack contains no documentation or community evidence describing Asana's subtask creation or task dependency/blocking-order features—it is entirely focused on API/developer platform capabilities, AI teammates, and unrelated community sentiment about UI/performance/Jira comparisons. Absence of evidence for this applicable, mainstream planning capability yields 'none'.

   ⚑ flag

   Jira~partialclaimed4/10

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

   proof ↗⚑ flag

7. engineerLog time directly against tasks and projects

   weight 2 · round drawn
   Asana—none0/10

   The evidence pack contains no mention of time-tracking or time-logging features against tasks/projects in Asana; it covers API, automation, AI teammates, and app components, none of which address engineer time logging.

   ⚑ flag

   Jira—none0/10

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

   ⚑ flag

Views organization

1. engineerHow the product performs and whether item caps apply in workspaces with tens of thousands of tasks

   weight 2 · round drawn
   Asana—none0/10

   No vendor documentation addresses item caps, workspace size limits, or performance characteristics at scale (tens of thousands of tasks); the evidence pack only contains generic API/AI-feature docs and anecdotal community complaints about poor performance (e.g., 'worst performing web app', suspected O(n^2) algorithms) with no concrete data or documented limits. This is an applicable engineering concern for a task-tracking tool, but no first-party or independent source quantifies scaling behavior or caps.

   • [community] “The funny thing is that Asana is possibly the worst performing web app out of all the ones I use on a regular basis. I have a strong suspici…”
   • [community] “i dont understand why you would even listen to them, their website is such a piece of shit- terrible performance, terrible ui. maybe their i…”

   proof ↗⚑ flag

   Jira—none0/10

   No evidence pack item documents Jira's performance characteristics, scalability limits, or item/issue caps for large workspaces (tens of thousands of tasks); the marketing pages focus on features, integrations, and AI, not scale benchmarks. Community comments mention general slowness and UI bugs but never quantify performance thresholds or confirm/deny caps, so there's no concrete data point for engineers to rely on either way.

   ⚑ flag

2. engineerSwitch between board, list, calendar, and timeline views of the same work

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack contains no mention of Asana's board, list, calendar, or timeline views or any ability to switch between them—only API/developer platform docs and general community sentiment about the product. This is a fair axis for a work-management tool, but no evidence supports it here.

   ⚑ flag

   Jira✓fullclaimed8/10

   Jira's own feature page explicitly states users can view work as boards, lists, timeline, or calendars, directly matching the story. Missing for 10: no independent/hands-on corroboration of switching between these specific views or any friction encountered doing so.

   • [claimed-docs] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”

   proof ↗⚑ flag

3. engineerSave a filtered view of work and share it with a link

   weight 2 · round to Jira
   Asana—none0/10

   No evidence in the pack addresses saved/filtered views, custom fields/search filters, or shareable links to such views in Asana; the evidence is entirely about API, AI teammates, and general sentiment.

   ⚑ flag

   Jira~partialcommunity4/10

   Community evidence confirms Jira supports saved searches/filters via JQL (jira-comm-12, jira-comm-16, jira-comm-17), which is the core mechanism for this story, but one hands-on account calls creating a useful saved search 'so painful' it seems intentional, and no evidence pack item documents the actual 'share via link' workflow. missing for 10: first-party docs on saving/sharing filter links, confirmation that sharing works smoothly, independent corroboration beyond one critical anecdote.

   • [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.”

   proof ↗⚑ flag

4. engineerSearch across all tasks, docs, and comments and get fast, accurate results

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack contains no mention of Asana's search feature across tasks, docs, and comments, nor any data on search speed or accuracy; it only covers API access, automations, AI teammates, and general product sentiment unrelated to search. This is a fair axis for a planning/tracking tool, but no supporting evidence exists.

   ⚑ flag

   Jira~partialcommunity3/10

   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…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Asana—none0/10

   No evidence in the pack discusses data residency, regional storage options, or data locality controls for Asana; the pack covers API/dev tooling and AI Teammates features only. missing for 10: any mention of region selection, data residency policy, or geographic storage controls.

   ⚑ flag

   Jira—none0/10

   No evidence in the pack addresses data residency, region selection, or hosting location controls for Jira; all citations focus on features, integrations, and general community sentiment unrelated to data residency.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Asana—none0/10

   No evidence pack item addresses AI training data opt-out, data usage policies for AI/ML model training, or any privacy controls specific to preventing data use in training. Evidence covers API docs, AI Teammates features, and general community sentiment, none of which touches this axis. Missing for 10: explicit documentation of an AI-training opt-out/opt-in setting, data processing terms addressing model training, and any admin control to restrict data use for AI training.

   ⚑ flag

   Jira—none0/10

   No evidence pack item addresses AI-training data opt-out or data-usage controls for AI model training; all citations concern features, integrations, or general product sentiment. Missing for 10: any documentation of an AI-training opt-out/data-processing addendum, admin controls to exclude data from model training, or policy statements on this topic.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Asana—none0/10

   No evidence pack items address data retention policies, deletion controls, or data lifecycle management for AI features/agents; only general API, developer sandbox, and AI Teammate governance mentions (audit trail, permissions) are present, none of which describe retention/deletion controls.

   ⚑ flag

   Jira—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy/data-lifecycle settings for AI-native use; all citations concern features, integrations, and general community sentiment. Missing for 10: documentation of data retention policy controls, deletion APIs/settings, and AI-specific data handling/retention configuration.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Asana—none0/10

   No evidence pack items mention telemetry, usage tracking, opt-out settings, or privacy controls for AI features; the pack covers API/developer docs and general community sentiment only.

   ⚑ flag

   Jira—none0/10

   No evidence pack items mention telemetry opt-out, usage tracking controls, or privacy settings for AI features in Jira; all citations concern general features, integrations, or unrelated community complaints.

   ⚑ flag

Ai insights

1. ai-native userAsk AI a question and get an instant answer with citations from my workspace content

   weight 2 · round to Asana
   Asana~partialclaimed4/10

   Asana markets 'Asana Dash — Your AI Chief of Staff' and AI Teammates that draw context from the Work Graph and shared memory, suggesting an in-workspace Q&A assistant, but no evidence describes citation of specific workspace items in answers or an 'ask a question, get instant answer with citations' UX. Missing for 10: explicit documentation of citation/sourcing behavior in AI answers, hands-on or independent verification of accuracy/citations.

   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Jira—none0/10

   Evidence shows Rovo AI features focused on automations, trend identification, and connecting assets (jira-docs-4, jira-docs-15, jira-docs-18), but there is no evidence of a conversational Q&A interface that returns instant answers with citations from workspace content. Missing for 10: any documentation of a 'Rovo Chat' or Q&A assistant, citation/sourcing mechanism, or hands-on example of asking a question and receiving a cited answer.

   • [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.”
   • [claimed-docs] “Rovo AI connects relevant assets and rich data from Confluence, Figma, and your 3rd party apps to your work.”

   proof ↗⚑ flag

2. ai-native userHave AI draft a project or initiative status update from recent activity

   weight 2 · round to Asana
   Asana~partialclaimed4/10

   Asana markets AI Teammates and 'Asana Dash - Your AI Chief of Staff' plus AI Studio automations that could plausibly draft updates from activity, and a developer tutorial exists for generating reports of status updates, but no evidence explicitly confirms an AI feature that drafts a project/initiative status update from recent activity. Missing for 10: a concrete first-party doc or demo showing AI-generated status update drafting, and independent/community confirmation it works as described.

   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”

   proof ↗⚑ flag

   Jira~partialclaimed3/10

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

   proof ↗⚑ flag

Dashboards

1. product managerBuild dashboards and widgets to report on project progress

   weight 2 · round to Jira
   Asana~partialclaimed3/10

   The evidence pack only shows API-level access to status updates for building custom reporting apps (asana-docs-4, asana-docs-9), not any native dashboard/widget-building UI for PMs to visualize project progress. Missing for 10: documentation of Asana's built-in Reporting/Dashboards or Portfolio charting features, native widget customization, and any hands-on evidence of PMs actually building such dashboards.

   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool.”
   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”

   proof ↗⚑ flag

   Jira~partialclaimed6/10

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

   proof ↗⚑ flag

2. product managerRoll up progress across multiple projects into a single portfolio view

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack contains no documentation or references to Asana's Portfolios feature, cross-project rollups, or multi-project dashboards — only API/developer docs, AI teammate marketing, and unrelated community sentiment. Missing for 10: any docs-1 or product page describing portfolio creation, progress rollup, or multi-project status aggregation.

   ⚑ flag

   Jira~partialclaimed5/10

   Docs gesture at cross-project visibility (jira-docs-8 'connect engineering, product, and marketing initiatives...across every team', jira-docs-14 'visibility on company's progress towards top priorities') implying some portfolio-level rollup, but there's no explicit mention of a dedicated portfolio/roadmap aggregation feature (e.g. Advanced Roadmaps) or any independent/hands-on confirmation that multi-project rollups actually work well in practice. Missing for 10: explicit documentation of a portfolio/roadmap rollup feature, independent or hands-on evidence corroborating cross-project aggregation, and community confirmation it performs adequately at scale.

   • [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] “Stay up-to-date on the work's progress using the view you like: boards, lists, timeline, or calendars.”

   proof ↗⚑ flag

Access control

1. product managerReview an admin audit log of actions taken across the workspace

   weight 2 · round drawn
   Asana—none0/10

   The evidence only mentions an audit trail scoped to AI Teammate/agent actions (asana-docs-13), not a workspace-wide admin audit log of user actions that a product manager could review for security purposes; no docs on an Admin Console audit log feature are present.

   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Jira—none0/10

   No evidence pack items mention an admin audit log, activity history, or security event tracking feature for Jira; only SSO/SAML and general feature marketing are cited. missing for 10: any documentation of an admin audit log, audit event types, retention/export, or access controls around it.

   ⚑ flag

2. product managerAssign granular permissions and roles to control who can view or edit work

   weight 2 · round to Jira
   Asana—none0/10

   The evidence pack contains no documentation of Asana's actual user-level permission/role system (e.g., project privacy settings, member roles, task-level view/edit controls). The closest mention (asana-docs-13) is about governance of AI Teammates/agents, not human-user granular permissions, so it does not substantiate this story. Missing for 10: docs on project/task privacy settings, member role definitions (admin/editor/viewer), and any independent confirmation these controls work as described.

   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Jira~partialclaimed4/10

   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”

   proof ↗⚑ flag

3. product managerCreate private sub-teams restricted to specific members

   weight 1 · round drawn
   Asana—none0/10

   No evidence in the pack addresses Asana's team/sub-team structures, privacy settings, or member restrictions; all documentation focuses on API, developer tools, and AI features. This is an applicable axis for a work-management tool but is unevidenced here.

   ⚑ flag

   Jira—none0/10

   No evidence in the pack addresses private sub-teams or member-restricted team/project access controls; only SSO/SAML and generic permission mentions appear, none specific to sub-team creation with restricted membership.

   ⚑ flag

4. engineerSecure organization access with SSO and SAML

   weight 3 · round to Jira
   Asana—none0/10

   The evidence pack contains no documentation or claims about Asana supporting SSO or SAML for organization access; all docs are about the API, integrations, and AI features. The only tangential mention (asana-comm-4) discusses a competitor's free Azure AD SSO, not Asana's own SSO/SAML capability, and does not confirm Asana ships this feature.

   ⚑ flag

   Jira~partialclaimed5/10

   Jira's feature page explicitly lists SAML & SSO as a security capability, confirming the feature exists, but the evidence pack lacks any detail on implementation, enterprise-tier requirements, or independent/hands-on confirmation. Missing for 10: documentation of setup/config details, tier restrictions (e.g., Enterprise-only), and third-party or community validation of SSO/SAML working reliably in practice.

   • [claimed-docs] “SAML & SSO”

   proof ↗⚑ flag

Trust reliability

1. product managerThe vendor's published uptime SLA and can check real-time incident status via a public status page

   weight 3 · round drawn
   Asana—none0/10

   No evidence pack item mentions an SLA, uptime guarantee, or a public status page with real-time incident reporting; all developer docs focus on API usage, deprecations, and app components rather than platform reliability commitments.

   ⚑ flag

   Jira—none0/10

   No evidence in the pack mentions an SLA or a public status page for Jira/Atlassian; all citations concern features, integrations, and general community sentiment. Missing for 10: any mention of published uptime SLA, status.atlassian.com or equivalent status page, or incident history.

   ⚑ flag

2. product managerThe vendor's documented support response times for each plan tier

   weight 2 · round drawn
   Asana—none0/10

   No evidence in the pack references support response times, SLAs, or plan-tier support commitments; all documentation relates to API, integrations, and AI features.

   ⚑ flag

   Jira—none0/10

   No evidence in the pack references support SLAs, response times, or plan-tier support commitments; all evidence covers product features, integrations, and general community sentiment unrelated to support response times.

   ⚑ flag