Update Macro after Jira project key change

[Deleted user]

Hi 

For a migration project, I had to change the project key in jira from 'DEV' to 'TDEV'. After that, I transferred the project to a new jira instance and updated the application links in Confluence so that it would find the correct project on the new server.

However, on the new server, there already is a 'DEV' project and it seems that Confluence simply used the alias after I renamed it to TDEV. So now that it can see the new server, all jira macro's are now referencing the wrong "DEV" project instead of the "TDEV" one that they actually should point to.

I'm guessing I have to update this via the confluence database (manually changing all macro's would take to long).

Any ideas which query I should use on the database? Or a different solution?

[Deleted user · Accepted solution]

I found the query based on the "bulk updating application links article"

I changed the query for updating the part of the macro that stores the project key and result was this: 

UPDATE BODYCONTENT 
SET BODY = REPLACE(BODY,'<ac:parameter ac:name="key">DEV-','<ac:parameter ac:name="key">TDEV-');