rovo and reading component descriptions

[Charles Liss]

Hey community,

It doesn't look like Rovo can access component descriptions.  This could be a powerful feature when paired with code access to support automated triage decisions.  Does anyone have advice or know if this is on the roadmap?

[Dr Valeri Colon _Connect Centric_]

@Charles Liss you’re not imagining it—today, Rovo’s Jira access is mostly limited to issue-level fields. While it can read component names, it typically doesn’t reliably access or use component descriptions in responses. This is a known gap rather than a configuration issue. If this is important for triage, a workaround is to:

• Surface that logic in custom fields or issue descriptions, or
• Use Automation / API to enrich issues with component metadata

Worth raising with Atlassian—this is a strong use case.

[Tomislav Tobijas]

Hi @Charles Liss ,

It hasn't been documented anywhere whether Rovo has access to this information/if it's able to read component descriptions. 👀

I haven't played with this specific scenario, but I'll move this question to the Rovo forum section so folks can chime in and take a look.
Rovo is primarily designed to read work item-level data, including the component name and potentially the ID.

It sounds like a useful feature, so it might be best to confirm with the support team whether this is a current limitation and whether something like that is on their roadmap. 🤔

I'm curious, though - are you using Jira components, or Compass components?

Cheers,

Tobi