Details
-
Bug
-
Resolution: Fixed
-
Low
-
7.12, 7.12.0
-
7.12
-
2
-
Severity 3 - Minor
-
Description
Summary
Upon trying to click on the View Issues link in the project statistics page, JIRA throws a null pointer exception and the issues fail to load.
This happens with any kind of project, Software or Business projects.
Environment
- JIRA 7.12.0 is installed and a project with at least 1 issue is created.
Steps to Reproduce
- Install JIRA 7.12.0
- Create a business project management project.
- Create 1 issue under that project and don't close it.
- Navigate to the project summary page (click on the project name to go to the summary page)
- switch the view from Activity (default) to Statistics
- On the statistics page, click on View Issues under Unresolved: By Assignee.
Expected Results
JIRA will open the issue navigator page and will display the issues unresolved by Assignee
Actual Results
JIRA fails to display the page and a 500 error is produced to the customer:
2018-09-05 11:44:13,580 http-nio-17120-exec-21 ERROR sherif 704x1475x1 aqz5j1 0:0:0:0:0:0:0:1 /issues/ [o.a.c.c.C.[.[localhost].[/jira7120].[action]] Servlet.service() for servlet [action] threw exception java.lang.NullPointerException at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper.lambda$static$11(JqlHelper.java:88) at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.visitors.SingleValueChecker.visit(SingleValueChecker.java:10) at com.atlassian.query.operand.SingleValueOperand.accept(SingleValueOperand.java:61) at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$expectOperand$4(ClauseChecker.java:52) at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$and$8(ClauseChecker.java:70) at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$and$8(ClauseChecker.java:70) at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$build$9(ClauseChecker.java:95) at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.lambda$visit$0(JqlHelper.java:198) at java.util.stream.MatchOps$1MatchSink.accept(MatchOps.java:90) at java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1812) at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:230) at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:196) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.anyMatch(ReferencePipeline.java:449) at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.visit(JqlHelper.java:198) at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.visit(JqlHelper.java:194) at com.atlassian.query.clause.TerminalClauseImpl.accept(TerminalClauseImpl.java:143) at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.lambda$doVisit$1(JqlHelper.java:210) at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:267) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
Notes
- On statistics page, View Issues under Unresolved: By Assignee links to:
http://localhost:17120/jira7120/issues/?jql=project+%3D+10000+AND+resolution+%3D+Unresolved+ORDER+BY+assignee+ASC%2C+priority+DESC%2C+key+ASC&mode=hide
All other statistics also fail like: Unresolved: By Component, Unresolved: By Priority, Unresolved: By Issue Type.
Only Status Summary works, and it is noticed that Status Summary* uses the project key rather than the numeric project id.
All the links work on JIRA 7.11. with exception of Unresolved: By Priority, which have a JQL bug, with a redundant priority in the query, but still, the issue navigator works fine and loads with no problem in JIRA 7.11.
- If we change the project id number to the Project key, the URL works and issue navigator is shown.
- This also occurs when trying to drill down on issues from the pie chart available on Dashboards.
Workaround
Need to create a custom set of filters that will return similar results and avoid using the links in the project statistics page.