Expanding ROVO Access in Jira Tickets

[Yousra A.]

Hello Community, 

I've been trying to use ROVO to enhance the content in my Jira ticket, including the content stored in Stagil Tables (addon). However, it seems like ROVO only reads from native custom fields and doesn't pick up any data from the tables or other non-standard elements.

Is there a way to make ROVO access and process all the content in the Jira ticket — not just the default custom fields?

Thanks!

[Nikola Perisic · Accepted solution]

Hello @Yousra A. , Rovo has built in connectors that allow to communicate with third party apps. Is this app belong to those built in connectors: https://www.atlassian.com/software/rovo/connectors

[Yousra A.]

Thank you for the reply @Nikola Perisic  , No I did not find it in the connectors,  but STAGIL tables is a Jira addon

[Nikola Perisic]

If that addon is not part of the Rovo connectors offered by Atlassian, Rovo can't read the data from it.

[Yousra A.]

I see, that doesn't  seem to be very useful. I thought ROVO can access everything in the JT. 

[Nikola Perisic]

Not really. Rovo doesn't have the access to third party application data. Only the data that is within the scope of Atlassian products which is legitemate. In the future, there should be more connectors included, but of course the data security regulations need to be passed first.

[Dr Valeri Colon _Connect Centric_]

Hi @Yousra A. — great question! Ya'll are on the right track, Rovo currently can’t access content from Marketplace apps like Stagil Tables. It only reads from native Jira fields, Confluence pages, and approved connected sources.

For now, a good workaround is to copy key info into Jira custom fields or linked Confluence pages. If you feel inclined submit or upvote a feature request.