Incorrect cached data causing Confluence Workbox not displaying updates from Jira

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Medium
    • No-Version
    • Affects Version/s: 6.13.4
    • Component/s: Core - Workbox
    • None
    • 5
    • Severity 3 - Minor
    • 1

      Issue Summary

      Updates from Jira instance, e.g. comments, mentions and shares don't show Workbox notifications in Confluence.

      Environment

      Both Confluence & JIRA instance have been integrated to one another via Application Link and Workbox Notifications have been configured to include Jira notifications as well.

      Steps to Reproduce

      On the Jira instance:

      1. Leave a comment with an @ mention to a user in a Jira issue
      2. Open the Workbox with that user in Confluence

      Expected Results

      New updates are being displayed in the configured Confluence Workbox notifications.

      Actual Results

      New updates aren't being displayed in the configured Confluence Workbox notifications, with no apparent errors thrown in either atlassian-jira.log or atlassian-confluence.log files.

      With the debug logging enabled (com.atlassian.mywork) in both Confluence and Jira, we could see the below exception is thrown in the atlassian-jira.log file:

      2020-07-12 20:02:07,671-0600 http-nio-8081-exec-22 url:/jira/rest/api/...DEMO-333/comment username:test DEBUG test 10.20.32.60,0:0:0:0:0:0:0:1 /rest/api/2/issue/DEMO-333/comment [c.a.m.client.service.HostServiceImpl] HostIdCache contained [REGISTERED_HOST] none()
      

      Cause:

      By default, the mywork-confluence-host-plugin do have preventive mechanism which will force refresh this cache value should the existing value is NULL as shown in the code snippet below.

      HostServiceImpl.java
          private Option<ApplicationLink> lookupAppLink(final HostType hostType) {
              final Option<ApplicationId> hostId = hostIdCache.getHost(hostType.name());
              if (hostId != null) {
                  log.debug("HostIdCache contained [{}] {}", hostType, hostId);
                  return hostId.flatMap(toAppLink);
              } else {
                  log.debug("HostIdCache didn't contain any info on [{}]; forcing a refresh of host info", hostType);
                  return updateHostAvailability().get(hostType);
              }
          }
      

      However, as what we've observed from the log snippet above - the HostIdCache is currently being recognised as not NULL since its current value is set to none(). Because of this, the force refresh mechanism then won't be triggered by mywork-confluence-host-plugin automatically. This is a bug in the mywork-confluence-host-plugin.

      Workaround

      Currently there is no known workaround for this behaviour. A workaround will be added here when available

            Assignee:
            Yaroslav Stanislavchuk (Inactive)
            Reporter:
            Lauretha Rura
            Votes:
            5 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: