Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Rovo
  • Questions
  • Automation with Rovo AI and Confluence fails when publishing a Jira version (no error details shown)

Automation with Rovo AI and Confluence fails when publishing a Jira version (no error details shown)

Marcial Gonzalez
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 14, 2025

Hello everyone,

I’m trying to create an automation rule that generates Release Notes in Confluence automatically when a new version is published in Jira.

Here’s what my rule does:

  1. Trigger: “When version is published” (filtered by regex for Hotfix versions, e.g. 24.4.10.1).

  2. Condition: Project equals XXXX

  3. Action 1: Use Rovo AI Agent (“GDP – Release Notes”) to generate release note content based on the issues linked to the version, using {{version.name}}.

  4. Action 2: Publish a new page in Confluence (space: Release Notes), with title Hotfix SP > {{version.name}} and body including the Rovo response.

However, when I publish a version (for example 24.4.10.1), the rule fails with status “Some errors”.
The audit log doesn’t show any useful details — it just says “Some errors occurred, please review component compatibility”.

I already tried:

  • Removing loops (“For each smart value”)

  • Testing with lookupIssues instead of version.issues

  • Using only one space and parent page

  • Reconnecting the Confluence and Rovo apps

But the result is always the same: the page is not created and the error is not shown in the audit.

Questions:

  1. How can I properly pass the output from Rovo to the Confluence “Create page” action?

  2. Is there any limitation when combining “Version published” trigger + Rovo Agent + Confluence action in the same rule?

  3. How can I get more detailed logs to understand which component fails?

Any advice or examples of a similar setup (Jira → Rovo → Confluence) would be appreciated.

1 answer

1 accepted

1 vote
Answer accepted
Rebekka Heilmann _viadee_
Community Champion
October 15, 2025

Hi @Marcial Gonzalezwelcome to the Community

I don't think it has something to do with Rovo but have you tried removing that action and simply putting a placeholder text as body on the Confluence page?

The Audit log should show which specific action fails.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events