-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
1
-
5
-
Currently, when we removed the summary field from JIRA's screen. It will cause an error when we cloning issue. JIRA will just keep loading when we cloning an issue. From the backend logs, we can see JIRA was encountering an error with Null Pointer Exception complaining Summary field was Null value. It would be glad if we can have a clear error shown in UI level when the user hit into this issue.
2019-01-28 11:02:41,820 http-nio-8080-exec-3102 ERROR [c.a.j.web.servlet.InternalServerErrorServlet] {errorId=e39caeab-b6be-4e85-a0da-57ea13845e41, interpretedMsg=, cause=java.lang.NullPointerException: null value in entry: summary=null, stacktrace=java.lang.NullPointerException: null value in entry: summary=null
at com.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:33) [closure-compiler-v20151216.jar:?]
at com.google.common.collect.SingletonImmutableBiMap.<init>(SingletonImmutableBiMap.java:39) [closure-compiler-v20151216.jar:?]
at com.google.common.collect.ImmutableBiMap.of(ImmutableBiMap.java:57) [closure-compiler-v20151216.jar:?]
It seems JIRA was expecting below when the summary was available on our screen:-
Above image is with screen configured with a summary field
Above image is when screen configured without a summary field
