Hi everyone!

I'm a developer at Atlassian that worked on this particular bug 5 years ago. It was actually solved and released back then, but it looks like I forgot to update this ticket - I'll close it off now. Unfortunately due to changes in the cloud architecture, it has reappeared in a slightly different form and that is probably what you're noticing. We're currently tracking this new version of the bug at ID-6349.

If you want to vote or get new updates, please follow that ticket.

Sorry for the inconvenience caused, having personally spent a lot of time on this bug I do know how frustrating this issue is for many of you.

Jeremy Evans
Senior Developer

How can we vote for something that is already resolved.  Please deploy Atlassian.  We may have to stop using confluence and cancel our licenses if we can't get this to work.

If the resolution has been completed, why hasn't it been deployed in 5 years. 

Would be interested why this hasn't been released yet. This is a big blocker for us to make certain content in Confluence public.

What is going on with this issue?  I am running into the same problem.

Is this fix being released anytime soon? This is a major inconvenience for our organization.

Jiras permission hierarchy for confluence (it's not a joke, ppl):
1. Administrators
2. SW users
3. Everyone in the whole world
4.Jira support portal users
This just looks silly to me. We have started using confluence for our release notes, and our trusted customers cannot see it, but everyone else can. I see it is pending, but get it out there. If not, at least we have to find another supplier for this. We don't deal in silly..

It's disappointing to see this still isn't fixed! Other than purchasing equivalent user tier, the workarounds do not solve the issue of when users log into the service desk to create an issue they are not given hints and links to confluence pages.

This issue is now tracked here - https://jira.atlassian.com/browse/CONF-30161

Linked CONF-2871, solving that would resolve this issue.