Problem / Opportunity

As more organizations interact with Atlassian services programmatically through Rovo and MCP (Model Context Protocol) connections, attachments remain "opaque" blobs. Data that arrives as an attachment (e.g., a CSV export, a log snippet, a delimited text file) can't easily be read, queried, reported on, or automated against, either in the Jira UI or by AI agents/MCP clients. Today that data has to be manually re-keyed into fields or parsed by external tooling.

Suggested Feature

Provide a Rovo-based capability that converts a ticket attachment into structured data stored on the issue, so the content becomes first-class, queryable data rather than an inaccessible file.

Why it's valuable

• Makes attachment data usable in JQL, automation rules, reports, and dashboards.
• Unlocks AI-assisted and MCP-driven workflows, agents can act on the content of attachments, not just their metadata (directly complements current MCP limitations where binary/attachment content isn't exposed).
• Reduces manual re-entry and error-prone copy/paste of tabular data into tickets.