ROVO is not generating correct output as per the context provided

[Kumarprem Gade]

ROVO should generate the RCA for my Jira tickets however it is not generating for the current context ticket.

[Jason Krewson]

Hey Kumarprem,

Are you using Rovo Chat or a Rovo Agent?

• If an agent can you share more details like the instructions,, skills, and so on?
• If chat, can you send us what your prompt was when asking?
  • Maybe we can test the same or give advice on how to structure the ask better.
  • For example I wouldn't ask for an RCA on a work item, I would personally type in root cause analysis, though AI probably does understand RCA it's always good to be clear. I work at a place that over uses acronyms and half the time I don't know what they mean and when I look them up, most the time AI and Google doesn't also lol.

[Jason Krewson]

Also as we are on the topic of Rovo I wanted to see if you were aware of the free Atlassian live training on Rovo, they are fantastic. I think I attended all of them and highly recommend doing so.

Class calendar 

[Dr Valeri Colon _Connect Centric_]

@Kumarprem Gade Welcome to the community. If you want the RCA for the ticket you’re currently viewing, make that context explicit: “Using only this work item and its related comments/history, generate a root cause analysis.” Rovo Chat can use the current Jira work item as context, but vague prompts may pull broader organizational knowledge. If it still analyzes the wrong ticket, share whether you’re using Chat or a custom Agent and how you’re invoking it.

[Kvitka Martsynyshyn]

A few things can affect Rovo's responses, including the amount of context available in the ticket, permissions to related issues or knowledge sources, and how the prompt is structured. Is Rovo producing a generic RCA, an incorrect one, or no output at all? Also, is this happening with a single ticket or across multiple Jira issues? Those details will help narrow down the cause.