Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to connect Jira project to Confluence Space

When I created my new Jira Cloud, Kanban, team-managed project in Jira, it created a new Confluence space and linked it to my new project. I navigated to the Pages view in Jira and clicked the "Connect different space or page" button on the top right of the screen to select a different Space to link my Jira project to. I selected my personal Confluence Space and it responded with, "We're having trouble displaying project pages. Something went wrong while trying to display pages from your connected Confluence space. Contact support if refreshing doesn't fix things."

How is this resolved? 


1 answer

0 votes
Christopher Maxwell
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 24, 2023

Hi @Matt Richards , and welcome to the Atlassian Community!

I suspect the issue here has to do with it being a personal space. I tested this in my Jira->Confluence, and when I went to "connect different space or page", I never saw my personal Confluence space listed in the options. Yet, apparently you did.

Did the connection from Jira->Confluence work properly for the first/regular Confluence space?


-- Christopher

Thanks for your reply @Christopher Maxwell . It did work initially and if I point it to any other Space now it works, so I agree that it may have something to do with it being my personal space. Sadly, that realization doesn't get me closer to a resolution.

Being on the free plan while I trial this with my org, it does not allow me to contact Atlassian support about this bug. 

How do us free users get help with an obvious bug?

Christopher Maxwell
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 25, 2023

Hi @Matt Richards ,

Very true, it doesn't solve the issue, although, the more info that can be gathered about how a bug functions and how to replicate it, the better.

To answer your question: how do us free users get help with an obvious bug?

For free plans, the only support option is here in the Atlassian Community. Atlassian staff regularly monitor the forums, and Atlassian staff members can open official bug reports.

I have an idea for you that I believe will help you get a bug report in to Atlassian.

Here is what I recommend you do:

  • Mark this ticket as answered to close it. This ticket is titled "Unable to connect Jira project to Confluence Space". The title is somewhat generic, and I am not sure it would stand out to any Atlassian staff member as being noteworthy because you are able to connect your Jira project to Confluence Space (just not the 2nd time to your personal space).
  • Next, I would make sure you can replicate the issue in a new Jira + Confluence free plan with replication steps and a screenshot or two.
  • Then, open a new ticket here in the Atlassian Community titled something like "Confirmed bug: unable to connect Jira Project to Confluence Personal Space on 2nd attempt (includes replication steps)" -- or something along those lines. On the ticket, include your replication steps and the screen shots.

I believe a ticket with that title and information stands a VERY good chance of attracting the attention of Atlassian staff. An Atlassian staff member will be able to clearly see there is a confirmed bug and it will be easy for them to replicate your same steps and then open an official bug report.


Speaking of Atlassian support on the paid plans, though, I will put in a plug for them. In my experience, Atlassian tech support is unapparelled. I have been involved in tech for about 25 years, and have utilized a wide variety of tech support. I have yet to experience any organization that provides the type of support that Atlassian does. Whether it's a bug, or figuring out a issue, or even trying to achieve a specific goal within Jira - they have been amazing. Granted, the solution to the problem is sometimes a "feature request" that I have to vote for - and there have been times I was frustrated to have a feature which worked fine in the old system be removed in the new system and turned into a "feature request" - but tech support would find the feature request for me so I could vote for it and comment on it. While with other tech organizations I have occasionally experienced good support from a tech or two, with Atlassian it has consistently been every experience with every tech.

There is no way that level of support is cheap - so I understand why Atlassian only provides that support for paid plans.

I also appreciate that Atlassian offers the free plan for up to 10 users. Not only does this allow small organizations to benefit from the Jira experience, but it also is a great way for people to test out the platform.

I hope this helps!
-- Christopher

I appreciate the thoughts. While I understand not offering 1:1 support to non-paying users and I am grateful for the free trial, as product person I find it odd that they would not create an easy means for users of any type to submit a bug report. One would think they would be motivated to know about these things. 

The process you describe may very well get the eyes of a dev lurking in the forums, but should users really have to go through that much trouble to only hope their feedback is noticed? 

Thanks again!

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events