Confluence space linked from Jira Software Docs tab does not persist after refresh

[Marissa Marks]

I created a new Confluence space from within a Jira Software project using the Docs/Pages area. The space was created successfully and is visible in Confluence, but the Jira project does not retain the link to it.

When I reload the Jira project’s Docs tab, it says no Confluence space is linked. If I link the space again, documents briefly appear on the screen, but after refreshing the browser or leaving the page and returning, Jira again shows that no Confluence space is connected.

I also tried removing the Jira connection from the Confluence side and re-adding it, but the link still does not persist.

Expected behavior:
Once a Confluence space is created or linked from the Jira Software project, the Jira Docs tab should continue showing that linked space after refresh/navigation.

Actual behavior:
The linked Confluence space appears temporarily, then disappears after refresh/navigation, and Jira shows no Confluence space connected.

[Marissa Marks]

Support ticket raised: https://support.atlassian.com/requests/PCS-3781834/

[Alexander Nilsson]

Hello Marissa,

the symptom you describe, where the space connects fine and is then gone again after a refresh, is a known one. Two separate things can cause it, so it is worth ruling out the permission cause before assuming a defect.

Per Atlassian's documentation, the documented cause of this exact symptom is a permission or product-access gap on the linked space. The account viewing the Docs tab either lacks View permission on that Confluence space, or does not have product access to Confluence. When that is the case, Jira does not show a broken-link warning, it just renders the tab as if nothing is connected, which matches what you see after each refresh. The link can be stored correctly and still look absent.

Two things to check first, both from the Confluence side, for the account you are actually testing the Docs tab with:

• Space access. Open the space directly at your-domain.atlassian.net/wiki/spaces, then go to Space Settings and Space Access, and confirm the account is in a group that grants View on that space.
• Confluence product access. Even with space permission, the account needs product access to Confluence, otherwise the check on reload comes back negative and the tab shows nothing connected.

The official article that covers this exact symptom and the fix is here:

https://support.atlassian.com/jira/kb/project-pages-does-not-load-with-error-space-or-page-not-found/

If you confirm the account clearly has both space View permission and Confluence product access and the link still drops on every refresh, then you are likely past the permission cause. There was a confirmed Jira-side bug with precisely this behaviour, JRACLOUD-84082, which Atlassian marked as Resolved with resolution Fixed in February 2025. Since that ticket is already closed, a current recurrence is best raised directly with support so they can look at your specific instance rather than tracking a closed issue:

https://support.atlassian.com/contact/#/

Greetings,

Alex

[Marissa Marks]

Hi Alex, 

Thanks for the reply. By "account" do you mean user? If yes, then I can confirm access is not an issue. I'm a licensed user to both tools, and system admin. Even then, I am explicitly listed as an admin in both the Confluence and Jira spaces. Its interesting to note too, as I was trying to submit a bug for this, the AI suggested trying a different space. I tried to link an established place, either the URL field in Space details and via the docs tab. 

I'll submit a bug!

Thanks, 
Marissa

[Alexander Nilsson]

Hello Marissa,

raising the ticket is the right call here, especially since you have cleanly ruled out the permission cause as a system admin with explicit admin on both the Jira and the Confluence side.

Furthermore what you are describing is an exact match to a bug Atlassian already logged and closed. Since that fix shipped over a year ago and you are seeing the exact symptom now, it is worth telling support directly that this looks like a regression of JRACLOUD-84082 rather than a fresh "links do not persist" report. That framing tends to get the case to the Confluence integration team faster, and it gives them a known-good reference point to compare your instance against.

https://jira.atlassian.com/browse/JRACLOUD-84082

If support comes back with a cause or a fix, dropping a short note here would help the next person who runs into this. The public ticket is already closed, so it will not show new movement, and this thread is what people will find when they search the same symptom.

I am really looking forward to your feedback :)

Greetings,

Alex