NullPointerException summary=null when cloning an Issue
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
Summary
When attempting to clone some issues receiving a NullPointerException with summary=null in the Jira user interface (UI). For further details of the error, see "Diagnosis" section.
Environment
Jira Core, Jira Software, Jira Service Management.
Diagnosis
When trying to clone issues, the following is thrown in the Jira user interface (UI) captured using the HAR file:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
java.lang.NullPointerException: null value in entry: summary=null
at com.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:32) [guava-26.0-jre.jar:?]
at com.google.common.collect.SingletonImmutableBiMap.<init>(SingletonImmutableBiMap.java:42) [guava-26.0-jre.jar:?]
at com.google.common.collect.ImmutableBiMap.of(ImmutableBiMap.java:72) [guava-26.0-jre.jar:?]
at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:124) [guava-26.0-jre.jar:?]
at com.atlassian.jira.bc.issue.DefaultIssueService$2.getFieldValuesHolder(DefaultIssueService.java:606) [classes/:?]
at com.atlassian.jira.issue.fields.SummarySystemField.validateParams(SummarySystemField.java:114) [classes/:?]
at com.atlassian.jira.bc.issue.DefaultIssueService.validateParams(DefaultIssueService.java:1116) [classes/:?]
at com.atlassian.jira.bc.issue.DefaultIssueService.validateClone(DefaultIssueService.java:620) [classes/:?]
at com.atlassian.jira.web.action.issue.CloneIssueDetails.doValidation(CloneIssueDetails.java:172) [classes/:?]
at webwork.action.ActionSupport.validate(ActionSupport.java:391) [webwork-1.4-atlassian-30.jar:?]
at webwork.action.ActionSupport.execute(ActionSupport.java:162) [webwork-1.4-atlassian-30.jar:?]
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) [jira-api-8.20.1.jar:?]
...........
At the same time, the following is thrown in Jira application log:
1
2
3
4
5
6
7
8
9
10
11
12
2021-12-27 00:00:00,909+0000 http-nio-8080-exec-100 ERROR [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet [action] in context with path [] threw exception [java.lang.NullPointerException: null value in entry: summary=null] with root cause
java.lang.NullPointerException: null value in entry: summary=null
at com.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:32)
at com.google.common.collect.SingletonImmutableBiMap.<init>(SingletonImmutableBiMap.java:42)
at com.google.common.collect.ImmutableBiMap.of(ImmutableBiMap.java:72)
at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:124)
at com.atlassian.jira.bc.issue.DefaultIssueService$2.getFieldValuesHolder(DefaultIssueService.java:606)
at com.atlassian.jira.issue.fields.SummarySystemField.validateParams(SummarySystemField.java:114)
at com.atlassian.jira.bc.issue.DefaultIssueService.validateParams(DefaultIssueService.java:1116)
at com.atlassian.jira.bc.issue.DefaultIssueService.validateClone(DefaultIssueService.java:620)
at com.atlassian.jira.web.action.issue.CloneIssueDetails.doValidation(CloneIssueDetails.java:172)
... 2 filteredExplanation: The error stack trace found above shows that on CloneIssueDetails, it will perform a quick SummarySystemField validation, and when the summary value is found to be null, it'll throw the exception.
Cause
The error is thrown because the "Summary" field is required to create an Issue, however, the said field is not present.
In this example, the "Summary" field was not configured in the "Create Issue Screen."
The following feature request has been submitted to provide a clearer error message in the Jira UI JRASERVER-68784 - JIRA Should Prompt A Correct Error In UI When Summary Field Was Not Included In JIRA's Screen
Solution
Ensure the "Summary" field exist and is present when creating an issue.
In this example situation, add the "Summary" field to the "Create Issue Screen"
Was this helpful?