How can I make Rovo agent use a custom template I generated?

[Veronica Rodriguez]

Hi,

I am trying to set up an agent on Rovo to help with QA tasks. What we need is an agent that creates a manual test plan on a confluence page when a ticket is provided. For the format we have generated custom templates that we use. 

I've tried to tell the agent to use the template but it does not manage to pick up the formatting. 

The template works perfectly when used manually when creating a page, but when used with the agent it results in badly formatted tables, it does not pick up "STATUS" type tags, hints or line brakes.

Eg: it publishes stuff like

| iOS | You may wanna bullet point the results and listed here for each device<br>{status:colour=Green|title=Use this to input the positive result}<br>{status:colour=Yellow|title=Use this to input a non-expected result} | | :--- | :--- | | Android | You may wanna bullet point the results and listed here for each device<br>{status:colour=Green|title=Use this to input the positive result}<br>{status:colour=Yellow|title=Use this to input a non-expected result} |

[Tomislav Tobijas · Accepted solution]

Hey @Veronica Rodriguez ,

It might be that this is a current limitation in how Rovo agents handle some Confluence artifacts and elements, such as templates. There's this feature request (related to improvements) that you can take a look at: ROVO-443: Support Macros and other artifacts via Rovo Agent creation 👀

Few things you can try:

• Define structure in instructions - Explicitly define the expected table structure and provide a markdown example of the table within the agent's instructions
• If you already have a final page example, tell the agent to follow the same format (like, just reference one or multiple pages with same structure)
• If you're using it in automation, I think you can use something like {{agentResponse.adf}} as per these docs.

Or, in the end, you can try to refine it and use follow-up prompts to refine the layout 🤔

Still, there are some hiccups, such as this one, that need some polishing.

Cheers,
Tobi

[Monika Ambrozowicz_Seibert_]

Hi @Veronica Rodriguez, I've come across your question and although I can see you've already got a highly relevant answer, there is something I would still like to add. For what you need (automatically create a Confluence page from Jira using a predefined structured template), I feel like there is a better solution than Rovo, at least for now, because the formatting issues you're seeing with Rovo are a known limitation of how AI agents interact with Confluence's wiki markup and macros.

On the other hand, if you are open to marketplace apps, AutoPage fits your need entirely. Full disclosure: I am affiliated with the team behind the app but I have seen users with similar use cases being satisfied with this solution. You could use the template your team has already built - and only add macros from AutoPage to automatically populate them with data from your Jira tickets. When a ticket comes in, the page is created with the correct formatting, not raw markup.

Another advantage that Rovo or Jira Automation don't offer (at least afaik) is the fact that this link is live - if someone makes an edit on Jira, the linked Confluence page gets updated in real-time. 

It won't replace the Rovo agent entirely if you need AI-generated content in the page body, but for the structured parts of your test plan (the tables, status indicators, device rows), this approach will give you consistent, correctly-formatted output every time.

If you have any questions, I'd be happy to help.