Continuous warnings "Application link for JiraIssueEvent not found" in the Jira logs

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

Problem

The Jira logs are spammed with warnings similar to:

1 Application link for JiraIssueEvent not found: com.atlassian.devstatus.vcs.JiraPullRequestEvent@19080f06[type=MERGE,initiator=com.atlassian.devstatus.EventInitiator@54451d8b[emails=[jsmith@example.com],username=jsmith,displayName=John Smith,resource=https://bitbucket.example.com/users/jsmith,avatar=https://bitbucket.example.com/users/jsmith/avatar.png?s=128&v=1502910614000],issueKeys=[CS-3904, CS-7547, CS-6667],entity=com.atlassian.devstatus.EventEntity@48b3f2d0[id=<null>,displayId=#5863,resource=https://bitbucket.example.com/projects/CASH/repos/cashregister/pull-requests/5863],sourceId=0b82bc95-8747-3636-a4f5-e9725ef4269f,sourceUrl=https://bitbucket.example.com]

The warnings are logged for the following event types (and potentially more):

  • com.atlassian.devstatus.vcs.JiraBranchEvent

  • com.atlassian.devstatus.vcs.JiraCommitEvent

  • com.atlassian.devstatus.vcs.JiraPullRequestEvent

Cause

The root cause of the problem is unclear, but it is most likely related to unclean AppLinks data in the database. The warning does not impact the functioning of the Bitbucket to Jira integration.

Workaround

Re-installing the AppLinks between Jira and Bitbucket helps get rid of the warning.

ℹ️ The AppLinks features will not work while AppLinks is uninstalled. Everything should fall back in place after the reinstallation, and no additional configuration is needed.

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.