Rovo Agent cannot return working image URLs from Jira issue comments in release notes workflow

[Maybe Gil]

Hi everyone,

I'm building a Rovo Agent to automate release notes generation. The goal is to enrich each release note Confluence page with not just a text description, but also a visual image, specifically, screenshots or images that testers attach in Jira issue comments when they approve the functionality.

What I'm trying to achieve:

• The agent scans issues included in a Confluence page release notes

• For each issue, it looks at the comments (particularly from testers during approval/QA)

• It extracts any images or image URLs attached to those comments.

• It includes both a description and the visual image in the final release notes.

The problem:

The Rovo Agent successfully identifies and locates the images in the issue comments. However, when it tries to return them:

• The image URL it provides is broken (returns a 404 or fails to load)

• Or the image shows as "preview is not available"

This happens consistently, regardless of whether the image was pasted inline in the comment or uploaded as an attachment. The agent clearly "sees" the image metadata, but the URL it constructs or retrieves doesn't resolve to an accessible image.

What I've tried:

• Asking the agent to return the direct attachment URL

• Asking for the thumbnail URL instead

• Different prompt variations to extract the image link

My environment:

• Jira Cloud

• Rovo Agent (custom)

• Images are added by testers as inline screenshots or attachments in issue comments

What I'd like to know:

1. Is this a known limitation with how Rovo handles Jira attachment/image URLs?

2. Are attachment URLs behind authentication that prevents the agent from returning a publicly resolvable link?

3. Has anyone found a workaround to get working image URLs from Jira comments via a Rovo Agent?

Any help or pointers would be really appreciated. Being able to include visual proof alongside the description in release notes would be a huge improvement for our stakeholders.

Thanks in advance!