-
Bug
-
Resolution: Fixed
-
High
-
7.4.1, 7.6.0
-
None
-
2
-
Severity 2 - Major
-
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
- Insert a Jira macro on a page
- Enter JQL to get a list of Jira issues
- Click `Display options`
- Search and select `Epic Name` (don't select `Epic Link`)
- Save the macro
- 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`
- is related to
-
CONFSERVER-60050 Custom Fields are missing in Jira Issue Macro after upgrade to Confluence 7.4.1, 7.5.0, 7.6.0
- Closed
- relates to
-
CONFSERVER-56017 Regression - JIRA Issues Macro fetching unnecessary fields from JIRA
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...