Create JIRA Issue from Applinks Assigns the Reporter as the Admin User
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
Symptoms
After installing an applinks connection, an issue created in JIRA under the user who created the applink (the admin user), not the currently logged in user.
Cause
The applinks connector is using basic authentication. It's possible that application links have been configured in both directions, from JIRA to Confluence and vice-versa.
Resolution
Delete the applinks from both JIRA and Confluence.
Reset the applink. Configure trusted applications authentication rather than basic. See Linking to Another Application.
See Also
Atlassian recommends OAuth
All new Application Links are created using OAuth. It provides all of the functionality of Trusted Applications and Basic Authentication. OAuth allows applications to authenticate and authorise users without accessing their credentials.
Further Reading
Was this helpful?