Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-60029

Jira Macro doesn't display`Epic Name`, `Epic Colour` and `Epic Status` values

    XMLWordPrintable

    Details

      Description

      Issue Summary

      It seems a regression according to customer report. The epic name field only exists in epic type issues, which seems not handled well.

      Steps to Reproduce

      1. Insert a Jira macro on a page
      2. Enter JQL to get a list of Jira issues
      3. Click `Display options`
      4. Search and select `Epic Name` (don't select `Epic Link`)
      5. Save the macro
      6. Publish the page

      Expected Results

      A list of issues on the page

      Actual Results

      Jira macro throws a error on the screen

      Data cannot be retrieved due to an unexpected error.
      View these issues in Jira
      

      In log (sensitive information removed)

      2020-08-20 15:05:05,912 ERROR [JIM Marshaller:thread-7] [extra.jira.helper.JiraExceptionHelper] throwMacroExecutionException Macro execution exception:
       -- url: /c741/display/PROJ/JIM+Here | page: 65609 | traceId: c76719074ee884db | userName: admin | referer: http://localhost:6741/c741/pages/resumedraft.action?draftId=65610&draftShareId=66387d08-a626-42fb-bad3-8a7e4764b824& | action: viewpage
      java.lang.NullPointerException
              at com.atlassian.confluence.extra.jira.JiraIssuesMacro.getEpicInformation(JiraIssuesMacro.java:839)
              at com.atlassian.confluence.extra.jira.JiraIssuesMacro.populateTableEpicData(JiraIssuesMacro.java:708)
              at com.atlassian.confluence.extra.jira.JiraIssuesMacro.populateContextMapForStaticTable(JiraIssuesMacro.java:977)
              at com.atlassian.confluence.extra.jira.JiraIssuesMacro.createContextMapFromParams(JiraIssuesMacro.java:450)
              at com.atlassian.confluence.extra.jira.JiraIssuesMacro.execute(JiraIssuesMacro.java:1238)
              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:183)
              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.util.concurrent.FutureTask.run(FutureTask.java:266)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
              at java.lang.Thread.run(Thread.java:748)
      

      Workaround

      Change `Epic Name` to `Epic Link`

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              qpham@atlassian.com Quan Pham
              Reporter:
              zxu2@atlassian.com Zac Xu
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: