Issue Summary

When a Rovo Agent generates responses or comments referencing users (such as currentUser, Reporter, or Service Desk Agents) directly on a Jira work item, the user references render inconsistently.

Instead of rendering as rich, interactive @-mentions, the output often displays as plain text or static hyperlinks. Adding explicit formatting instructions to the Agent's system prompt (e.g., instructing the Agent to use shorter Account IDs instead of full Cloud IDs) yields inconsistent results, with mention rendering stopping intermittently even after initially appearing to work.

Steps to Reproduce

1. Configure a Rovo Agent in Studio to generate comments or content on Jira work items referencing specified users (e.g., Reporter, currentUser).
2. Include system prompt instructions requiring user references to be formatted as @-mentions, like:
   • Create a customer-facing reply, and you must use a shorter Account ID for the user, which Jira requires for the mention to trigger correctly when pasted instead of the full Cloud ID.
3. Trigger the Agent to generate a comment on a Jira work item.
4. Observe how user references are rendered in the generated comment.

Expected Results

Referenced users are consistently rendered as fully interactive, rich @-mentions across all user types and execution attempts on Jira work items.

Actual Results

User mention formatting is intermittent and inconsistent. User references frequently render as plain text or generic links rather than interactive @-mentions, even when explicit system prompt rules regarding Account IDs are provided.

Workaround

Correct the reply manually before pasting it on the ticket