Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Make Rovo able to read work items from a linked Jira instance

Kirstin Seidel-Gebert
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 10, 2026

Hi community!

We have a Jira/Confluence cloud instance, and, additionally, a separate cloud instance for our customer-facing documentation.
These two instances are linked by an application link (Jira --> Confluence DOC and Confluence --> Confluence DOC).

Nevertheless, I don't seem to to be able to get Rovo on Confluence DOC read work items from Jira. It always claims to not have access.

Is there a known limitation that this is not possible - let Rovo read tickets from a linked instance?

Hope that someone can shed a light on this!
Cheers,
Kirstin

3 answers

1 accepted

3 votes
Answer accepted
Tomislav Tobijas
Community Champion
August 10, 2026

Hi @Kirstin Seidel-Gebert ,

I believe this is a known limitation as stated in following suggestions/reported limitations:

Now, we have not had this case before, but I could potentially test it out next week to see if there are any workarounds you could use 👀

You could maybe find some ideas on links above - either provided by Atlassian staff or by other customers 🤔

Cheers, Tobi

1 vote
Kirstin Seidel-Gebert
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 10, 2026

Thanks, Tobi!
I voted and added a watch.

The workaround I used was to paste the content of the work item description to the Rovo chat. This was OK in this case because the item did not have any comments yet.

Cheers,
Kirstin

0 votes
Chris Stevens MFG
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 1, 2026

Hi @Kirstin Seidel-GebertI get the issue. You don’t want everyone seeing the same Confluence content just because it comes from the same place.

One option is separate spaces and permissions in Confluence, but that can get messy if the real goal is different customer-facing sites.

I’ve just added support for this in Satori Cloud. You can use one Confluence connection and publish different pages/page trees to separate sites for customers, partners, developers, etc.

Disclaimer: I’m building Satori Cloud.

https://updates.satoricloud.com/publish-different-confluence-content-for-different-audiences/

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events