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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,465,224
Community Members
 
Community Events
176
Community Groups

JIRA Issue links do not resolve on Confluence pages after migration to cloud

Edited

Our jira and confluence server instances were recently migrated to cloud.

When being on server, I had a lot of Confluence pages that had JIRA issue links (simply copied from the browser address bar and pasted into the Confluence page). These links resolved into a formatted jira issue link after pasting (no specific macro was used). So, the end result was, when the page was saved, the links showed nicely and displayed the icon of the JIRA issue along with the title of the issue.

After migration to cloud, all of these confluence pages started showing this in places where the links to the jira issues were mentioned: 

'jira' : Unable to locate JIRA server for this macro. It may be due to Application Link configuration 

What can be done to fix these pages all at one go? Why are these links appearing to be broken? Is the new formatter on Confluence cloud not backward compatible? As I said I simply pasted the links into the pages, no specific macro used. Why isn't the Cloud migration accounting for these simple things and users need to fix them (if that is the only way out)? JIRA links should resolve regardless before / after migration.

Is this an issue with the formatter on Confluence Cloud or a jira-confluence application link configuration issue?

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS

Atlassian Community Events