Old Jira Application name displaying while authenticating Confluence from the Jira under User Profile
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
A user can authenticate confluence from Jira to show confluence-related activities under "Activity Stream" on the profile page.
If for some reason the Jira application is renamed and the application link between Confluence and Jira is recreated, then on re-authenticating Confluence from Jira under Activity Streams it still displays the Old Jira application name.
In the below screenshot, Jira Application was renamed to "Jira Dev Old", but still the old name "Jira Dev" is displayed while authenticating
Cause:
On changing the Jira application name from the UI under System => General Settings => Title,
oauthconsumer DB table is not updated and retains the entry with the old consumer name, as a result, the same is passed to confluence during the recreation of the APP link after the Jira application name change.
As a result, there is an incorrect entry in the bandana DB table of confluence against the property name for the new App link configuration.
Diagnosis
Run the below query in the Confluence DB
1
select * from bandana where bandanavalue like '%Old_Jira_Name%' ; If an entry like the one below with property name="name" indicating the old Jira Application name is returned, it indicates confluence is holding the incorrect Application name for the Jira
Solution
Delete application link in confluence with Jira. Also, do the same in Jira and verify old link doesn't exist anymore on either side.
Confluence
Confirm by running the below query in confluence DB that you don't get the output for the below query like the one you received last time:
1select * from bandana where bandanavalue like '%Old_Jira_Name%' ;JIRA
Stop the Jira application
Run the below update statement in Jira DB
1update oauthconsumer set consumername='New_Jira_application_Name' where id=<ID of Incorrect Entry in oauthconsumer for Old Jira Application Name> ;Start Jira
Recreate the application link between Jira and confluence.
Try to authorize confluence again from Jira to verify if you can see the correct application name now.
We strongly recommend running the direct DB updates after taking a DB backup first.
Was this helpful?