Confluence fails to render Jira issues macro when user timezone set to three letter identifier

XMLWordPrintable

    • 7
    • Severity 3 - Minor
    • 1

      Issue Summary

      When a users timezone is set to any three letter timezone identifier while in view mode, a Jira Issue macro displays an error to the user and in atlassian-confluence.log.

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Setup Confluence v7.17.2 8803, and Jira v8.22.2 822002.
      2. Create an application link.
      3. Populate Jira with sample issues.
      4. Create a new Confluence page with a Jira macro, and publish it.
        • The macro populates with issues as Expected.
      5. Change the personal timezone setting in the user profile page to one of the options listed below:
        Name Identifier
        (GMT-1000) Hawaii HST
        (GMT-0900) Alaska AST
        (GMT+0100) West Central Africa ECT

       

      1. Revisit the newly created page
        • The macro now no longer populates with issues.

      Expected Results

      The macro populates with issues that match the provided JQL.

      Actual Results

      The macro remains empty, and displays the following errors:

      UI Error:

      Data cannot be retrieved due to an unexpected error.

      [View these issues in Jira]

      Log Error:

      2022-05-26 20:37:00,598 ERROR [JIM Marshaller:thread-21] [extra.jira.helper.JiraExceptionHelper] throwMacroExecutionException Macro execution exception: 
 -- url: /confluence/display/PD/Test+Page | page: 1081346 | traceId: d9a7d38727550f6f | userName: admin | referer: https://example.com/confluence/pages/editpage.action?pageId=1081346 | action: viewpage
java.time.zone.ZoneRulesException: Unknown time-zone ID: HST
	at java.base/java.time.zone.ZoneRulesProvider.getProvider(ZoneRulesProvider.java:279)
	at java.base/java.time.zone.ZoneRulesProvider.getRules(ZoneRulesProvider.java:234)
	at java.base/java.time.ZoneRegion.ofId(ZoneRegion.java:120)
	at java.base/java.time.ZoneId.of(ZoneId.java:408)
	at java.base/java.time.ZoneId.of(ZoneId.java:356)
	at com.atlassian.confluence.extra.jira.JiraIssuesMacro.setupContextMapForStaticTable(JiraIssuesMacro.java:997)
	at com.atlassian.confluence.extra.jira.JiraIssuesMacro.populateContextMapForStaticTable(JiraIssuesMacro.java:908)
	at com.atlassian.confluence.extra.jira.JiraIssuesMacro.createContextMapFromParams(JiraIssuesMacro.java:474)
	at com.atlassian.confluence.extra.jira.JiraIssuesMacro.execute(JiraIssuesMacro.java:1170)
	at com.atlassian.confluence.extra.jira.executor.StreamableMacroFutureTask.renderValue(StreamableMacroFutureTask.java:74)
	at com.atlassian.confluence.extra.jira.services.DefaultAsyncJiraIssueBatchService.lambda$processRequestWithJql$2(DefaultAsyncJiraIssueBatchService.java:184)
	at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:38)
	at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContextInternal(VCacheRequestContextManager.java:84)
	at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContext(VCacheRequestContextManager.java:68)
	at com.atlassian.confluence.vcache.VCacheRequestContextOperations.lambda$withRequestContext$1(VCacheRequestContextOperations.java:59)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

      Tested using:
      Confluence: v7.17.2 8803
      Jira: v8.22.2 822002

      Workaround

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

            Assignee:
            Unassigned
            Reporter:
            Atlas Foulks
            Votes:
            9 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: