Rovo can't tag someone properly in a Jira issue from Confluence

Question

I was using Rovo to analyse a feature design on confluence and asked to the tool to summarize the review points, add them as a comment to the jira ticket, and tag a particular user in the ticket

What I got was an unintelligible ['account ID'] in the jira comment and no notification posted to the intended target user.

When I asked Rovo why it pointed out a fundamental design limitation in the SW that meant this basic 'tag a user' would never work. It's recommended solution was for me to go an manually edit the comment and tag the person.

BOOM - there goes the automation!

So….what's the go here people?

Anwesha Pan · Answer

Hi @Andy Atkinson👋🏻

When you manually type @username in Jira, the Jira Cloud editor inserts a structured Atlassian Document Format (ADF) Mention Node, whereas most AI agent tools and REST API endpoints submit comments formatted in Markdown or plain text strings. When Rovo tries to mention someone, it passes the resolved Account ID as text which causes the issue.

You could try one of the below options as workaround:

Option 1: Pair Rovo with Jira Automation (Recommended)

Instead of having Rovo write the final comment with mentions, let Jira Automation handle the notification:

* Ask Rovo to summarize the design and add the comment with a specific identifier or update a custom field.
* Create a Jira Automation rule (e.g., When comment added containing "Design Summary" / When Issue updated):* Action: Send email / Slack message or Add comment using native Smart Values:

Attention [~accountid:{{issue.assignee.accountId}}], here is the latest Rovo summary:

* Jira Automation’s [~accountid:...] syntax is natively compiled into active ADF mentions by the automation engine and will trigger notifications.

Option 2: Use Jira Issue Assignee / Watcher Roles

* If the person you are trying to tag is the Assignee, Lead, or a Watcher on the ticket, any comment added by Rovo will automatically notify them as part of their standard Jira issue update notifications without needing an inline mention.

Option 3: Notify via Connected Chat (Slack / MS Teams)

* If your Jira and Confluence spaces are connected to Slack or MS Teams, have the workflow post the summary to the shared project channel, where @username via webhook or bot integrations are natively supported.

I hope this helps & resolves your issue. 🙂

Thanks,

Anwesha

Matthew Sinclair · Answer

This is rather funny - not sure if bug or Rovo having an off moment!

If you where to use Jira Automation to tag a user - the "Account ID" is required - but an additional tag is required to make it a mention - or at least something to that effect. (I had to write it down - naturally can't remember outside my work instance <laugh>)

Only suggestion I have is to see if Rovo can (re-re-)edit the post to correct the error on it's own. I've had situations where Rovo gives me something - and 2 redo's later it finally figures it out - then I tell it "Remember this!".

I'll have to try this in our instance during my shift - I'll let you know what I find out. Should be good for a laugh at least!