Confluence workbox notifications linking to old JIRA site URL

[Heather Gates]

Our organization initially had JIRA but not Confluence. We recently added Confluence but used a different account because we were changing who paid. After connecting the accounts, we migrated JIRA to the new URL. The accounts were successfully connected. Links back and forth work exactly as expected with the exception of the Confluence workbox notification links going back to JIRA. Those links (and only those) are still pointing to the old JIRA URL.

We removed the links and re-linked JIRA to Confluence and Confluence to JIRA trying to force the workbox JIRA links to update, but nothing changes.

[Dario B]

EDIT: I have linked the wrong bug. Adding the correct one with the correct work-around:

Maybe a bit too late... but this looks the same as:

- https://jira.atlassian.com/browse/CONFCLOUD-53830

Also, if this is the case, try to check if this is helping:

Search for the id of the row containing the wrong data (old JIRA is the old JIRA hostname. E.g. jira.something.com):

select * from "AO_9412A1_AOREGISTRATION" where "DATA" like '%JIRA_URL%';

Write down the ID of the returned row(s), then run below queries (replace ID_FROM_PREVIOUS_QUERY with the ID you got from the previous query):

update "AO_9412A1_AOREGISTRATION" set "DATA" = replace("DATA", '"displayURL":"https://OLD_JIRA"', '"displayURL":"https://NEW_JIRA"') where "ID" = ID_FROM_PREVIOUS_QUERY;

Then:

update links set destpagetitle = replace (destpagetitle, 'OLD_JIRA', 'NEW_JIRA'); 

update links set lowerdestpagetitle = replace (lowerdestpagetitle, 'OLD_JIRA', 'NEW_JIRA');

update bodycontent set body = replace (body, 'OLD_JIRA', 'NEW_JIRA');

Finally, Re-index and flush the cache.

I hope this helps...

Cheers,

Dario

[Andy Ballon]

I know this is an old thread but, we encountered a similar issue. We upgraded a linked jira and the workbox notification link is still pointing to the old jira url.

What's the best way to fix this? Thanks

[Dario B]

EDIT: I have linked the wrong bug. Adding the correct one with the correct work-around:

Maybe a bit too late... but this looks the same as:

- https://jira.atlassian.com/browse/CONFCLOUD-53830

Also, if this is the case, try to check if this is helping:

Search for the id of the row containing the wrong data (old JIRA is the old JIRA hostname. E.g. jira.something.com):

select * from "AO_9412A1_AOREGISTRATION" where "DATA" like '%JIRA_URL%';

Write down the ID of the returned row(s), then run below queries (replace ID_FROM_PREVIOUS_QUERY with the ID you got from the previous query):

update "AO_9412A1_AOREGISTRATION" set "DATA" = replace("DATA", '"displayURL":"https://OLD_JIRA"', '"displayURL":"https://NEW_JIRA"') where "ID" = ID_FROM_PREVIOUS_QUERY;

Then:

update links set destpagetitle = replace (destpagetitle, 'OLD_JIRA', 'NEW_JIRA'); 

update links set lowerdestpagetitle = replace (lowerdestpagetitle, 'OLD_JIRA', 'NEW_JIRA');

update bodycontent set body = replace (body, 'OLD_JIRA', 'NEW_JIRA');

Finally, Re-index and flush the cache.

I hope this helps...

Cheers,

Dario

[Jochen Suckfüll]

We have the same issue, using Confluence 5.9.4 and JIRA Software 7.1.1.

[Christophe Chenavier]

The same for us here. Is there any workaround ?