Best practice for Rovo agent to create ticket comments via automation rules - Link embedding issue

[#1]

Hello everyone,

I'm currently using a Rovo AI agent within a Jira Cloud automation rule to provide onboarding assistance for access requests.

Current implementation:

• Automation rule triggers the Rovo agent with ticket data
• In the automation rule, I use "And: Add comment to work item" action
• The comment content is set to {{agentResponse}}

Issue encountered: During testing, I've found that I cannot embed clickable links within the {{agentResponse}} when it's added as a comment. I've tried both formats:

• Markdown format: [text](URL)
• Jira format: [text|URL]

However, the links appear as plain text instead of being rendered as clickable links in the ticket comments.

Questions:

1. Is there a more efficient or recommended way for a Rovo agent to directly create comments on Jira tickets through automation rules?
2. How can I make the Rovo agent response include properly formatted, clickable links in Jira comments?
3. Are there specific formatting requirements for links in {{agentResponse}} variables?

Any guidance or documentation you can point me to would be greatly appreciated.

Thanks in advance!

[Rimantas Andrulevičius]

@Jordi Romera could you elaborate on the use case a bit more (I'm also in a similar case creating an access mng solution on JSM and having the gray area of onboarding how-to)?

I don't have an exact answer for your current case, but what I've seen is:

1. Try without any format (Jira should handle plain links and render them based on user settings)

2. Since you are using automation, I would suggest trying to use JSON format and make a smart value ->variable (or use advanced branching) out of the response:

https://youtu.be/BmjCyM--etk?si=br8M8cms644efYlW&t=1351

https://community.atlassian.com/forums/Automation-questions/Rovo-Agent-Response-String-To-JSON/qaq-p/3045634

[Martin Fischer]

Hi @Jordi Romera,

I did a quick test with a simple Rovo Agent that just returns a Confluence documentation link, and another one that grabs any link it finds within the Jira work item. Both worked well in Jira comments — plain HTTP/HTTPS links are automatically detected and rendered as clickable, no extra formatting needed.

For example, I used a prompt like:

“You are an assistant that takes information from Confluence about the Azure Sync app, providing a link to the documentation, and returns the link in a format that can be clickable within Jira comments.”

or

“You are an assistant that takes any link you can find within this Jira work item and returns it in a format that is clickable within Jira comments.”

That was enough for Jira to handle the link properly:

Of course, if you need more control over formatting (e.g., forcing specific markup or richer output), you might want to look into creating a custom Rovo Agent using Forge. That gives you finer-grained control of the response payload.