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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs