'File not found' when accessing a Rovo-generated attachment

Question

From Rovo in confluence I asked the tool to generate a summary of a doc review and post it as an attachment to a jira ticket for a colleague to review.

The attachment was generated (.md) and attached to the ticket (as a hyperlink). I could download the attachment, but my colleague got 'File not Found'.

What's going on here? The intent was to add the attachment to the jira ticket just like any other attachment. Has Rovo created a link to a private 'AI chat file'?

Andy Atkinson · Answer

What I am looking for is a solution that can be fully automated. This is my expectation for any AI tools / workflow in a modern SDLC environment - seamless, reliable integration that allows the human step back, step upwards. So having Rovo automatically review material, create a summary, attach to a ticket tagging responsible parties is such a basic thing that should require zero manual involvement.

Anyway, thanks for the response - this simply looks like a 'product gap' with Rovo and proper Atlassian suite integration (so sits with their Product Managers).

Josh · Answer

That behaviour matches how a lot of AI chat attachments work today: Rovo can create a file that is reachable for you (the person who ran the chat), but the link is not a normal Jira issue attachment that every collaborator can open.

Quick checks:

* On the work item, open the Attachments section (paperclip) — is the .md listed there as a real Jira attachment, or only as a URL/hyperlink in the description/comment?
* If it is only a hyperlink from the chat, ask a colleague with access to the same Confluence page to open that link while signed in — if they still get File not found, the object is almost certainly private to the chat/session.

Workaround that usually works: have Rovo put the summary into a comment or a short Confluence page (or paste markdown into the description), then attach a real file via the issue’s Attach files control. That creates a proper Media Store attachment with issue permissions.

If you can share whether the link host is something like a chat/media path vs the normal Jira attachment URL, that will confirm it. Worth a support ticket if Rovo advertised “attach to Jira” but only wrote a private chat file — that is a product gap.