monday.com vs Jira

Agent access

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

   weight 2 · round to monday.com
   monday.com~partialprobed6/10

   monday.com has extensive agent-oriented developer documentation (MCP server docs, agent APIs, webhooks, scopes) confirmed by both docs and a probe verifying the MCP docs page exists, but a direct probe shows no llms.txt file is served (404), so the specific 'point an agent at llms.txt' capability is absent even though broader agent-oriented docs exist. missing for 10: a working llms.txt endpoint, independent confirmation that agent-oriented docs are consumable/structured for LLM ingestion.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.monday.com/llms.txt”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
   • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”

   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 monday.com
   monday.com~partialclaimed6/10

   monday.com exposes a GraphQL API, SDKs, webhooks, and lets you 'run and manage every monday agent programmatically from your own code, anywhere you need it' (monday-docs-9, monday-docs-35, monday-docs-28), which supports scripted/headless automation. However there is no explicit documentation of CI/CD integration, headless test runners, or pipeline examples, and no independent verification that these APIs work reliably in automated pipelines. Missing for 10: explicit CI/CD documentation or examples, independent/hands-on confirmation of headless operation, and any mention of exit codes/scriptable non-interactive workflows.

   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”

   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
   monday.com—none0/10

   The evidence shows monday.com exposing its own hosted/developer MCP server so external agents (Claude, ChatGPT, etc.) can connect to monday, and monday's agents can be reached via multiple channels including 'our MCP' — this is monday acting as an MCP server/provider, not monday consuming third-party MCP servers to extend its own agents' toolset. There is no documentation of monday's agents importing or plugging in external MCP servers as tool sources.

   • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
   • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
   • [claimed-docs] “Bring an agent in once and reach it from Slack, WhatsApp, Telegram, Make, our MCP, or the API. One identity, every surface — no rebuilding p…”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”

   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 monday.com
   monday.com✓fullprobed8/10

   Monday.com documents an official hosted MCP server with a dedicated docs page (confirmed by probe) plus first-party guidance on connecting agents from Claude, ChatGPT, etc. via this MCP endpoint, granular scopes, and managed secrets. Missing for 10: independent/hands-on third-party verification that the MCP server works as documented in practice.

   • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
   • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
   • [claimed-docs] “Work with tools like Claude, Copilot, and ChatGPT through official integrations or the monday MCP, and keep data secure with trusted AI conn…”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”

   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
   monday.com—none0/10

   The evidence pack covers monday's APIs, SDKs, MCP servers, and apps framework, but nowhere mentions an official CLI tool for developers or AI-native workflows. Since a platform of this kind could plausibly offer a CLI, absence of evidence means the axis is unmet rather than inapplicable.

   ⚑ 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 monday.com
   monday.com✓fullprobed9/10

   monday.com documents a full GraphQL API (monday-docs-35), SDKs (monday-docs-28), granular OAuth scopes and secret storage (monday-docs-6), webhooks/event subscriptions (monday-docs-7, monday-docs-27), and an official MCP server (monday-probe-2) alongside apps framework docs — giving AI-native users multiple documented, programmatic ways to drive the product. Missing for 10: no independent/hands-on developer corroboration of API robustness or reliability beyond first-party docs.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”

   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 monday.com
   monday.com✓fullclaimed7/10

   Docs explicitly describe requesting granular scopes (e.g. boards:read), storing keys in managed secret storage, admin-level scoping of each agent's board access, and audit logging of every action — directly matching scoped/least-privilege credential issuance for agents. Missing for 10: no independent/hands-on verification of scope granularity or credential rotation, and no detail on token expiry/revocation workflows.

   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001. Your data never leaves our secure servers.”

   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 monday.com
   monday.com✓fullprobed7/10

   Monday documents official SDKs/tooling for AI-native builders: a GraphQL API, an 'apps framework' for code-first development, an open-source React component library (Vibe) for native-looking UI, and a documented developer MCP server for scaffolding/deploying agents. Together these constitute a real official SDK/toolchain for building AI-native apps and agents on the platform. Missing for 10: independent/hands-on developer corroboration of SDK quality or adoption, and llms.txt returns 404 suggesting incomplete AI-facing doc tooling.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
   • [claimed-docs] “Build with Vibe, monday's open-source React components, and look native instantly.”
   • [claimed-docs] “Match monday with Vibe, our open-source React components, so your app looks native from day one.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.monday.com/llms.txt”

   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 monday.com
   monday.com✓fullclaimed8/10

   Docs explicitly describe webhook subscriptions to real-time board events (create_item, change_column_value, etc.) plus agent-triggering webhooks, backed by a GraphQL API for integration. Missing for 10: independent/hands-on verification of webhook reliability and payload details beyond vendor docs.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”

   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 monday.com
    monday.com~partialprobed7/10

    monday.com documents one persistent agent identity reachable across Slack, WhatsApp, Telegram, Make, MCP, and API 'no rebuilding per channel' (monday-docs-12), plus 2-way sync, webhooks, a unified Models API, and an official MCP server (monday-docs-1, monday-docs-2, monday-docs-17, monday-docs-31, monday-probe-2) that together support handing off work/context between tools and agents. Missing for 10: independent/hands-on verification that context is actually preserved across handoffs (all evidence is vendor docs), and no case study showing a real multi-tool handoff working end-to-end.

    • [claimed-docs] “Bring an agent in once and reach it from Slack, WhatsApp, Telegram, Make, our MCP, or the API. One identity, every surface — no rebuilding p…”
    • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
    • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
    • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
    • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”
    • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
    • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”

    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 monday.com
   monday.com~partialclaimed6/10

   Docs claim AI agents can surface deep intelligence, actionable insights, risk/progress gap detection, and automated reports/summaries directly in monday (docs-20, docs-21, docs-22, docs-23, docs-32), which matches the story of in-product AI-generated insights. However, evidence is entirely vendor marketing copy with no independent/hands-on validation of insight quality or accuracy, and community feedback focuses on performance/UX issues rather than AI insight capability. Missing for 10: independent verification of insight quality, concrete examples/screenshots of generated insights, and hands-on user reports confirming the feature works as described.

   • [claimed-docs] “Surface deep intelligence and actionable insights from any subject.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [claimed-docs] “Schedule meetings, summarize calls, and extract action items.”
   • [claimed-docs] “Score our open deals and send proposals to anyone above 80%.”

   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 monday.com
   monday.com✓fullclaimed8/10

   monday.com documents native automations (event triggers like create_item/change_column_value, real-time listeners), plus AI agents that run in isolated sandboxes managed by monday, scoped with permissions, audited, and triggered autonomously by mentions/assignments or scheduled reports (status updates on a set schedule). This directly supports background/autonomous automation setup. Missing for 10: independent/hands-on verification of autonomous background execution reliability and no community corroboration of agent-based automations specifically (community evidence is generic negative sentiment unrelated to this feature).

   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “You lead. Agents act.”

   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 monday.com
   monday.com✓fullclaimed8/10

   monday.com offers built-in AI agents that can be messaged, assigned items, and @mentioned to perform real work directly within the product ('Talk to agents like teammates... assign them items'), with docs describing creating custom agents via natural language and managing them from an admin dashboard. Community evidence is generic product criticism unrelated to the AI assistant feature, so it doesn't dispute this capability. Missing for 10: independent hands-on verification of agent quality/reliability and no third-party review of the assistant feature specifically.

   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Describe any workflow in your own words to create a unique agent in minutes.”
   • [claimed-docs] “Message them in updates, assign them items, and @mention them in any conversation to kick off real work — replies, statuses, and follow-ups …”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “You lead. Agents act.”

   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 monday.com
   monday.com✓fullclaimed7/10

   monday.com documents natural-language operation extensively: users can message, assign, and @mention agents in plain language to kick off real work, and can describe entire workflows in their own words to create agents. This directly matches the story of operating the product via natural-language commands. Missing for 10: independent/hands-on verification that NL commands reliably produce correct actions, and more detail on limits of NL understanding beyond marketing copy.

   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Describe any workflow in your own words to create a unique agent in minutes.”
   • [claimed-docs] “Message them in updates, assign them items, and @mention them in any conversation to kick off real work — replies, statuses, and follow-ups …”
   • [claimed-docs] “You lead. Agents act.”

   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 monday.com
   monday.com✓fullclaimed7/10

   monday's docs describe a dedicated agent-building capability: defining goals/rules in natural language, describing workflows to create custom agents, scoping board access, hosting/sandboxing, granular permissions, and monitoring via an admin dashboard (monday-docs-13, 14, 10, 5, 6, 9). This directly matches the story of building/configuring a custom AI agent within the product. Missing for 10: independent or hands-on verification that the agent builder works as described in practice, and detail on customization limits/complexity for non-technical users.

   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Describe any workflow in your own words to create a unique agent in minutes.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”

   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 drawn
   monday.com—none0/10

   The evidence shows monday has a GraphQL API and developer docs, but there is no mention of an interactive API reference, playground, or runnable code examples anywhere in the pack.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.monday.com/llms.txt”

   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 monday.com
   monday.com✓fullclaimed7/10

   monday documents an expressive GraphQL API for developers with public developer docs, which serves as a machine-readable/documented spec analog for programmatic access, though it's GraphQL rather than a formal OpenAPI/REST spec download. missing for 10: an explicit downloadable OpenAPI/Swagger file or schema export, and independent confirmation of spec completeness.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”

   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 monday.com
   monday.com~partialclaimed5/10

   Docs mention that agents deploy to 'isolated sandboxes monday manages' and that versions can be scaffolded and promoted from chat, implying a dev/test environment separate from production infra, but there is no explicit description of a sandbox for testing against non-production data or verification this isolation covers board/data-level testing. missing for 10: explicit sandbox/staging environment for data testing, independent or hands-on confirmation that production data is untouched.

   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”

   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 drawn
   monday.com—none0/10

   The evidence pack describes monday's GraphQL API, apps framework, and MCP integrations but contains no mention of API versioning scheme or a documented deprecation policy for its APIs. Missing for 10: explicit versioning scheme documentation, deprecation policy/timeline, changelog or migration guides.

   ⚑ 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
   monday.com—none0/10

   No evidence pack item documents specific API rate limits, request quotas, or concurrency caps for monday's GraphQL API, MCP server, or agent platform; docs mention general scopes and secret storage but never numeric or documented limits.

   ⚑ 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
   monday.com!disputedcontradicted4/10

   monday's GraphQL API, webhooks, and automation triggers (create_item, change_column_value) suggest programmatic bulk item manipulation is possible, but there's no explicit documentation of a batch/bulk operations endpoint, and independent hands-on reports describe the platform struggling and crashing once boards exceed a few thousand items (up to ~20k before failure), directly undercutting claims of smooth operation 'across many items at once'. Missing for 10: explicit bulk/batch API documentation, evidence of large-scale (10k+) item operations succeeding, and any first-party rebuttal to the scaling complaints.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”

   proof ↗⚑ 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 monday.com
   monday.com✓fullclaimed7/10

   monday.com's automation engine and agent framework support event-based triggers (create_item, change_column_value, real-time events, agent mentions/assignments) that fire automated actions, well documented across native automations and the developer platform. missing for 10: independent/hands-on verification of rule complexity and reliability at scale, and clearer detail on conditional logic depth beyond simple trigger-action pairs.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”

   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 to monday.com
   monday.com~partialclaimed5/10

   monday's docs mention scheduled automation only in the narrow context of status updates and performance reports ('Automate status updates and performance reports on a set schedule'), which supports recurring job scheduling but doesn't document a general-purpose recurring workflow/job scheduler for arbitrary AI-native automations. Missing for 10: explicit cron-like scheduling API/UI for arbitrary workflows, examples of recurring agent tasks beyond reporting, and independent confirmation of reliability at scale.

   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”

   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
   monday.com—none0/10

   Evidence covers agent building, deployment, MCP connectivity, and app scaffolding (with 'promote versions from chat' hinting at some deployment lifecycle), but there is no mention of automation version history, review workflows, diffing, or rollback of automations. No documented capability to revert an automation to a prior version.

   ⚑ 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 monday.com
   monday.com~partialclaimed5/10

   monday.com documents AI agents that can be assigned items, triggered on item creation/column changes, and used to "spot risks and progress gaps" or manage support tickets via Zendesk integration, which supports building an automated triage-like workflow, but there is no explicit documentation of an out-of-the-box 'triage and prioritize bugs' capability or example. missing for 10: a concrete bug/task triage workflow example, explicit prioritization logic, and independent/hands-on evidence that this works in practice.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Connect Zendesk or Active Directory to manage your support tickets in monday.com, helping teams resolve issues faster and keep customers hap…”

   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 drawn
   monday.com—none0/10

   The evidence describes monday's AI agents/automation framework (agent creation, MCP, integrations, admin scoping) but nothing about the assistant learning a user's tone, shorthand, or writing preferences to tailor output. Missing for 10: any mention of personalization/memory of user style, adaptive tone learning, or preference-based output customization.

   ⚑ 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. product managerBuild multi-step automations without writing code

   weight 2 · round to Jira
   monday.com~partialcommunity6/10

   monday.com's docs describe automation recipes (triggers like create_item/change_column_value, scheduled reports, agent assignment flows) that let a PM configure multi-step automations without code, and its no-code automation builder is a well-known core feature referenced via triggers/subscriptions. However, the evidence pack is heavily focused on the newer AI-agent/developer platform rather than the classic drag-and-drop automation board builder itself, and community feedback raises usability/reliability concerns that could affect building complex automations at scale. missing for 10: direct documentation of the classic visual automation recipe builder UI, independent hands-on validation of multi-step automation reliability, and confirmation that no coding is required for complex branching logic.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”

   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

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

   weight 3 · round to Jira
   monday.com~partialclaimed5/10

   Evidence shows trigger/event subscriptions (create_item, change_column_value) and scheduled automations for status updates/reports, which map to trigger-and-action rules, but the pack lacks documentation of monday's classic no-code Automations recipe builder (e.g., cross-board triggers, conditional actions, integration recipes) that engineers would typically use. Missing for 10: dedicated automation-builder documentation, examples of multi-step conditional recipes, and independent/hands-on validation that these rules reliably eliminate manual steps.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”

   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

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

   weight 2 · round to monday.com
   monday.com~partialclaimed6/10

   Docs show scheduled automation for reports/status updates and event-based triggers (webhooks on create_item, change_column_value, agent mentions), which together support building recurring/scheduled workflows for routine work. However, evidence doesn't detail monday's core automation recipe builder, cron-style scheduling controls, or monitoring/error-handling for these workflows. Missing for 10: detailed schedule configuration UI/API, recipe builder specifics, failure/retry handling, and independent confirmation of reliability at scale.

   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”

   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

4. 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
   monday.com—none0/10

   No evidence pack item discusses plan limits, rate limits, overage charges, throttling behavior, or hard stops for automation/API usage—only feature and integration descriptions are present.

   ⚑ 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
   monday.com—none0/10

   Evidence lists many integrations (Salesforce, GitHub, Slack, Zendesk, communication tools) and a general integrations marketplace, but nothing mentions Figma, Adobe XD, Sketch, or any design-tool-specific integration that would let a designer update project status directly from their design tool.

   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”
   • [claimed-docs] “Integrate Salesforce, Quickbooks, or HubSpot to manage leads, track opportunities, and keep your sales process proactive and results-driven.”
   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”

   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
   monday.com—none0/10

   The evidence pack covers monday's AI agents, integrations, MCP, and developer platform extensively, but contains no mention of a native Docs or notes feature for organizing shared documents alongside project boards. Absence of evidence for this applicable capability yields 'none'.

   ⚑ 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
   monday.com—none0/10

   No evidence pack item mentions commenting on specific text or images within an item's description; all documentation focuses on agents, integrations, boards, and infrastructure rather than inline commenting/annotation features.

   ⚑ 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
   monday.com—none0/10

   The evidence pack contains no documentation or claims about real-time sync of board changes across open sessions; all monday-docs items concern the AI agent/developer platform (MCP, webhooks, agents), not live collaborative UI updates. Community evidence discusses performance/slowness but not specifically real-time refresh behavior, so there's no basis to confirm the capability.

   ⚑ 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 to monday.com
   monday.com~partialclaimed5/10

   monday.com's 'Updates' feature (message, @mention, assign items 'in any conversation') is documented as a native in-item communication mechanism, and the platform also integrates with Slack/Teams/Gmail for broader team chat, suggesting engineers can converse without leaving the work-planning surface. However, the evidence pack frames this messaging capability almost entirely around AI agents rather than human-to-human team chat, and no first-party or independent source describes robust native person-to-person chat/threads as a core UX pillar. Missing for 10: explicit documentation of human team chat/threads within boards, independent corroboration of real-time chat usability, and evidence it's used as a primary chat tool rather than via external integrations.

   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Message them in updates, assign them items, and @mention them in any conversation to kick off real work — replies, statuses, and follow-ups …”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Integrate your org's communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”

   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

App ecosystem

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

   weight 2 · round to Jira
   monday.com—none0/10

   No evidence of a bi-directional sync with GitHub/GitLab/Jira-style issue trackers; docs focus on agents, MCP hosting, and generic integrations but never mention repo issue-tracker sync specifically.

   ⚑ 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
   monday.com—none0/10

   The evidence pack focuses entirely on monday's AI agent framework, MCP hosting, and integration channels for building agents—none of it describes a unified cross-tool task view pulling assigned tasks from multiple external project management tools (e.g., Jira, Asana, Trello) into one dashboard for an engineer. No integration or aggregation feature matching this story is documented.

   ⚑ 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 monday.com
   monday.com✓fullclaimed8/10

   monday.com documents native integrations for Slack, GitHub/GitLab, and Google (Drive/Calendar/Gmail) via its integrations directory, plus a broader library of 850+ apps/integrations and GraphQL API/webhooks for custom connections. Community evidence criticizes general performance/UX but does not contradict integration functionality specifically. Missing for 10: independent hands-on verification of these specific native connectors and any noted integration-specific limitations.

   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Work with tools like Claude, Copilot, and ChatGPT through official integrations or the monday MCP, and keep data secure with trusted AI conn…”
   • [claimed-docs] “Integrate your org's communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”

   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 monday.com
   monday.com✓fullclaimed9/10

   monday.com documents an app marketplace/integrations directory with 850+ apps and integrations (Salesforce, Slack, GitHub, Zendesk, etc.), no-code connection options, and flexible APIs/SDKs for custom integrations, directly matching the story. Community evidence cited is about general UI performance/usability complaints, not integrations, so it does not contradict this axis. Missing for 10: independent third-party verification of the marketplace's breadth/quality beyond vendor claims.

   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Integrate Salesforce, Quickbooks, or HubSpot to manage leads, track opportunities, and keep your sales process proactive and results-driven.”
   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”
   • [claimed-docs] “Connect Zendesk or Active Directory to manage your support tickets in monday.com, helping teams resolve issues faster and keep customers hap…”

   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 monday.com
   monday.com~partialclaimed6/10

   monday's developer docs explicitly support building custom board/item views, dashboard widgets, and full-page apps, and provide the Vibe React component library specifically to make custom UI 'look native instantly.' However, evidence is limited to vendor docs with no independent/hands-on corroboration of designer experience building these views, and community feedback focuses on core product usability rather than the custom-view/widget building workflow itself. Missing for 10: independent or hands-on verification of the widget-building experience, and details on design constraints/limitations designers encounter when building native-feeling views.

   • [claimed-docs] “Create custom board views, item views, dashboard widgets, and full-page apps.”
   • [claimed-docs] “Build with Vibe, monday's open-source React components, and look native instantly.”
   • [claimed-docs] “Add actions to the item, board, and column menus, right where work happens.”

   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
   monday.com—none0/10

   No evidence pack items mention workspace export functionality, or preservation of comments, attachments, or audit trails during export; all documentation focuses on agents, integrations, and MCP servers. Missing for 10: any documentation of an export feature, evidence of what data (comments/attachments/audit logs) is retained, and any hands-on or community confirmation of export fidelity.

   ⚑ 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
   monday.com—none0/10

   The evidence pack covers monday's developer platform, AI agents, and integrations but contains no mention of a guided onboarding walkthrough or first-time workspace setup flow for engineers. One community comment (monday-comm-10) even notes the product 'required too much setup and customization,' but this is not concrete counter-evidence of a documented walkthrough claim—there simply is no walkthrough feature evidenced.

   • [community] “I used monday.com a few years ago. Back then it was called 'dapulse'... I felt silly every time I said it. I just remember really wanting to…”

   proof ↗⚑ 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 to monday.com
   monday.com~partialclaimed3/10

   Evidence shows monday.com offers many third-party integrations (Salesforce, HubSpot, Zendesk, GitHub, etc.) and flexible APIs/SDKs that could be used to move data in from other tools, but there is no explicit mention of an import wizard, CSV import, or dedicated 'migrate from X' onboarding flow for switching PMs. Missing for 10: explicit import/migration tooling (e.g., CSV/board import, one-click migration from competitor PM tools), independent confirmation that data import actually works smoothly during onboarding.

   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”
   • [claimed-docs] “Integrate Salesforce, Quickbooks, or HubSpot to manage leads, track opportunities, and keep your sales process proactive and results-driven.”
   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”

   proof ↗⚑ 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
   monday.com—none0/10

   The evidence pack contains no mention of pre-built project templates, template galleries, or quick-start project setups for product managers; all docs items focus on AI agents, integrations, and developer/MCP features. missing for 10: any documentation of a template library, template selection during board/project creation, or industry-specific templates.

   ⚑ 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
   monday.com—none0/10

   No evidence in the pack addresses seat minimums or annual billing commitment terms; only a Free-plan credit-card mention is present, which does not answer the story's question about seat/billing enforcement.

   ⚑ 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 monday.com
   monday.com~partialclaimed6/10

   monday's GraphQL API, webhooks, granular scopes, and apps/MCP framework show broad programmatic access to boards, items, columns, and events, suggesting extensive API coverage of UI actions. However, there is no explicit claim or evidence that every UI capability (e.g., all board customizations, dashboard widgets, admin settings) is exposed via API, and no independent verification of API-UI parity. missing for 10: explicit vendor statement of full API/UI parity, independent test confirming coverage of edge-case UI features.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”

   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 drawn
   monday.com—none0/10

   The evidence pack contains no mention of a bulk data export feature, open-format export (CSV/JSON backup), or account portability tooling — only a GraphQL API for programmatic integration, which is not the same as a documented 'export everything and leave' capability. missing for 10: explicit data export/backup feature, open-format (CSV/JSON) full-account export documentation, any statement about data portability or account closure export.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”

   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
   monday.com—none0/10

   monday.com is a closed-source SaaS product; the only open-source item mentioned is 'Vibe' (a UI component library), not the core product's source code. No evidence of the platform's source being available under an open license.

   ⚑ 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

4. ai-native userSelf-host the core product

   weight 3 · round to Jira
   monday.com—none0/10

   monday.com is explicitly a managed SaaS/cloud platform — docs state agents and apps run on monday-managed infra ('Your syncs and tools run on our infra, not yours', 'Your data never leaves our secure servers') with no mention of any self-hosted deployment option. No evidence of a self-hostable core product exists in the pack.

   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001. Your data never leaves our secure servers.”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001.”

   proof ↗⚑ flag

   Jira~partialcommunity3/10

   Only evidence is a community comment mentioning running Jira on-prem, implying a self-hosted option exists but with performance caveats (e.g., Lucene index issues); there is no first-party documentation of a self-hosted/open-source edition, licensing, or install instructions in the pack. missing for 10: official self-hosting/Data Center documentation, deployment guides, licensing terms, independent corroboration of feature parity with cloud.

   • [community] “Also it's really annoying when I try to copy something from a ticket description but it starts editing the whole description field.”

   proof ↗⚑ flag

Mobile access

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

   weight 2 · round drawn
   monday.com—none0/10

   No evidence pack items mention a native mobile app or any mobile-specific functionality/parity claims; all docs focus on web platform, APIs, agents, and integrations. Community comments discuss performance/usability issues on the general product but say nothing about mobile app feature parity.

   ⚑ 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
   monday.com—none0/10

   The evidence pack contains no documentation of dependency-tracking features (e.g., linked items, dependency columns, Gantt/timeline views) that would let a PM coordinate cross-team dependencies; nearly all monday-docs items focus on AI agents/MCP integration, unrelated to planning dependencies. One community comment (monday-comm-4) explicitly states 'Linking tickets to one another in Monday is really bad, data gets lost all the time,' which is negative anecdotal evidence but there's no vendor claim of dependency tracking to formally dispute. Missing for 10: any first-party documentation of dependency/linking features, timeline/Gantt views, or cross-team coordination workflows, and any positive hands-on evidence of this capability working.

   • [community] “I use it at my current company. I don't like it. I don't like Jira either, but Jira is still far superior... Linking tickets to one another …”

   proof ↗⚑ 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
   monday.com—none0/10

   The evidence pack is dominated by AI-agent, MCP, and developer-platform documentation and contains no first-party or hands-on evidence describing monday.com's native field/column customization or workflow status editing capabilities for boards. While this is a fair axis for a work-management product, nothing in the pack concretely documents the ability to customize fields or workflow statuses, so it cannot be credited despite being a plausible feature.

   ⚑ 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
   monday.com—none0/10

   The evidence pack contains no documentation of monday.com's core board features (status columns, priority columns, owner/people columns) for tracking initiatives; nearly all provided evidence concerns the AI-agent/developer platform (MCP, agents, apps framework) rather than basic work-tracking functionality. Community evidence only speaks to general usability complaints, not specifically to status/priority/owner tracking.

   ⚑ 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
   monday.com—none0/10

   The evidence pack contains no mention of sprint planning, backlog management, story points, or agile-specific board templates for monday.com; it only covers AI-agent/MCP features, generic board views, and integrations (e.g., GitHub/GitLab PR linking) that don't address sprint/agile workflow support. Absence of evidence for this applicable planning-tracking capability means it cannot be credited as delivered.

   ⚑ 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
   monday.com—none0/10

   The evidence pack contains no documentation or community reports describing monday.com's core item/task creation, assignee, or due-date fields — nearly all first-party docs here focus on AI agents/MCP integration rather than basic task management, and community comments only vaguely reference 'items' and 'tickets' without confirming assignment/due-date workflows. missing for 10: docs on creating items with owner/assignee columns, due-date column functionality, and any confirmation of this core PM workflow.

   • [community] “Hmm maybe I missed something but isn't Monday some kind of do-all task management system? A client of mine forced us on it and the un-opinio…”
   • [community] “I use it at my current company. I don't like it. I don't like Jira either, but Jira is still far superior... Linking tickets to one another …”

   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
   monday.com—none0/10

   The evidence pack contains no documentation of subtask creation or dependency/blocking-order linking features (all docs items focus on AI agents, MCP, and integrations). The only relevant evidence is a community complaint that 'linking tickets to one another in Monday is really bad, data gets lost all the time' (monday-comm-4), which is negative rather than confirmatory, and there is no vendor claim in this pack to set up a dispute.

   • [community] “I use it at my current company. I don't like it. I don't like Jira either, but Jira is still far superior... Linking tickets to one another …”

   proof ↗⚑ 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
   monday.com—none0/10

   No evidence in the pack mentions time tracking, time logging columns, or timesheet features against tasks/projects; all citations focus on AI agents, integrations, and app-building framework. Missing for 10: any mention of a time-tracking column, timer widget, or timesheet reporting feature.

   ⚑ 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
   monday.com—none0/10

   No vendor documentation addresses item caps or performance benchmarks at scale; the only relevant evidence is a hands-on community report stating boards would 'struggle and finally crash after a few thousand items,' capping usable scale around 20k items, directly contradicting the story rather than supporting it.

   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”
   • [community] “I tried using Monday.com for a building project I had and the interface become totally unusably slow... no idea if this is fixed but it seem…”
   • [community] “We'd tried it for a little bit for a small 5-6 person team. It was slow as hell. Stopped using it.”

   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
   monday.com—none0/10

   The evidence pack only mentions building custom board/item views and dashboard widgets (developer platform for apps), not the native ability to toggle a single board's data between board, list, calendar, and timeline layouts. No citation confirms this specific multi-view switching capability.

   ⚑ 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
   monday.com—none0/10

   The evidence pack contains no mention of saved filtered views, view sharing, or shareable links for board/item views — all docs entries focus on AI agents, MCP, integrations, and APIs. This is a fair planning-tracking capability for a work OS product, but nothing in the pack demonstrates it.

   ⚑ 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
   monday.com—none0/10

   The evidence pack contains no mention of a search feature spanning tasks, docs, and comments, nor any performance/accuracy claims about search; instead it focuses on integrations, AI agents, and developer platform features. Search is a fair and applicable axis for a work management tool, but no supporting evidence exists here.

   ⚑ 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
   monday.com—none0/10

   Evidence mentions general infra security certifications (SOC2, HIPAA, ISO27001) and that data stays on monday's servers, but there is no mention of any region/data-residency selection option for customers. missing for 10: any documentation of selectable data regions, residency controls, or data-locality options.

   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001. Your data never leaves our secure servers.”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001.”

   proof ↗⚑ 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
   monday.com—none0/10

   No evidence pack item addresses opting out of AI model training or data usage policies for AI training; documentation covers security certifications (SOC2/HIPAA/ISO) and agent infrastructure but never mentions training data controls or opt-out mechanisms. Missing for 10: explicit AI training opt-out policy, data usage terms for model training, any admin toggle or contractual guarantee against training use.

   ⚑ 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
   monday.com—none0/10

   No evidence addresses data retention policies, deletion controls, or user ability to purge AI-related data; docs mention secure infra/compliance certifications but not retention/deletion controls specifically.

   ⚑ 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
   monday.com—none0/10

   No evidence in the pack addresses telemetry opt-out or usage-tracking controls for AI-native users; docs cover security/compliance certifications but not user-facing telemetry settings. Missing for 10: any documentation of a telemetry/usage-tracking toggle or opt-out mechanism.

   ⚑ 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 drawn
   monday.com—none0/10

   Evidence covers AI agents, integrations, MCP, and automation but nothing describes a workspace Q&A feature where a user asks a question and receives an answer with citations back to specific workspace content. Vague phrases like 'Surface deep intelligence and actionable insights' or 'Spot risks and progress gaps' do not describe citation-backed instant answers.

   ⚑ 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 monday.com
   monday.com✓fullclaimed7/10

   monday.com's own docs explicitly describe automating status updates and performance reports on a schedule, plus AI agents surfacing insights and spotting progress gaps, directly matching the story of AI drafting status updates from activity. Missing for 10: independent/hands-on verification of output quality and more detail on exactly how 'recent activity' data feeds into the drafted update.

   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [claimed-docs] “Surface deep intelligence and actionable insights from any subject.”

   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 drawn
   monday.com~partialcommunity6/10

   Monday's own docs explicitly state you can build custom dashboard widgets and views (monday-docs-3) and automate status/performance reporting (monday-docs-21) and surface risk/progress insights (monday-docs-22), directly matching the PM reporting story. However, there is no independent or hands-on validation of dashboard widget usability, and community reports describe severe performance degradation with large boards (thousands of items) which could undermine dashboard reliability at scale. missing for 10: independent corroboration of dashboard-building workflow, evidence dashboards remain performant/usable at scale, concrete examples of widget types used for reporting.

   • [claimed-docs] “Create custom board views, item views, dashboard widgets, and full-page apps.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”

   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
   monday.com—none0/10

   The evidence pack is almost entirely about monday's AI agents, MCP/developer platform, and third-party integrations, with no documentation of a portfolio-level rollup view aggregating progress across multiple projects/boards. General integration claims (e.g., monday-docs-33) refer to cross-platform data sync, not a PM-facing portfolio dashboard.

   ⚑ 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 to monday.com
   monday.com~partialclaimed4/10

   Docs mention admins can 'audit every action' an AI agent takes as part of agent governance, implying some audit logging exists, but there's no evidence of a general admin audit log covering all user/workspace actions (logins, permission changes, item edits) as a PM would expect for security review. missing for 10: evidence of a comprehensive audit log covering human user actions across the workspace, not just AI agent activity; independent/hands-on confirmation of audit log usability.

   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”

   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
   monday.com—none0/10

   The evidence pack only discusses scoping and auditing AI agent board access (e.g., monday-docs-10, monday-docs-6) and general integration/security certifications, but contains no evidence of human-facing granular roles/permissions (viewer/editor/guest, board-level access control) that a product manager would assign to team members. Missing for full credit: documentation of user role types, board/item permission settings, or admin controls for human collaborators.

   ⚑ 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
   monday.com—none0/10

   No evidence in the pack discusses private sub-teams, member-level board restrictions, or team-based access controls within monday.com's workspace/board permission model; all evidence pertains to AI agents, MCP, integrations, or general product sentiment.

   ⚑ 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
   monday.com—none0/10

   No evidence pack items mention SSO, SAML, identity providers, or authentication standards for organizational access; all docs focus on agents, MCP, integrations, and infra certifications (SOC 2, HIPAA, ISO 27001) rather than SSO/SAML specifically. Missing for 10: any documentation of SSO/SAML support, identity provider integration (Okta, Azure AD, etc.), or admin configuration for enterprise authentication.

   ⚑ 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
   monday.com—none0/10

   No evidence pack item mentions an uptime SLA or a public status page for monday.com; all docs relate to integrations, agents, and infra certifications, not incident transparency. missing for 10: published uptime SLA, public status page URL, real-time incident history.

   ⚑ 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
   monday.com—none0/10

   No evidence in the pack mentions support response times, SLAs, or tiered support commitments for any monday.com plan; the evidence covers product features, integrations, and community sentiment unrelated to support SLAs.

   ⚑ 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