You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
A bit of a special case here but maybe others have come across a similar scenario. We're going to be in the middle of a migration of our JIRA and Confluence systems soon, with JIRA moving significantly earlier than Confluence. This will break all JIRA issue macros on our Confluence pages, and I have reached out to the JIRA admins of the new system. We will not be allowed to create an application link from our current Confluence to the new JIRA system.
So this will leave our Confluence environment with a lot of broken JIRA issue macros. Are there any options to bulk update something like this? Or perhaps is my best option to somehow disable/turn off all JIRA issue macros? Even disabling them may not be viable since even if the macro is disabled, there will likely still be disabled macro warnings on the pages themselves.