-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
None
-
None
Summary
Accessing certain reports in JIRA Agile causes an exception to be thrown.
Steps to Reproduce
Access a Sprint Report when there are no issues in the sprint history and the board is configured to use Time Tracking.
Expected Results
The board displays as normal.
Actual Results
This exception is thrown:
2014-11-16 09:22:37,955 http-bio-8080-exec-100 ERROR anonymous 562x39015x5 p0625q 10.137.114.5,10.137.115.6 /rest/greenhopper/1.0/rapid/charts/scopechangeburndownchart.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: clauseValues is empty java.lang.IllegalArgumentException: clauseValues is empty at com.atlassian.jira.util.dbc.Assertions.not(Assertions.java:186) at com.atlassian.jira.jql.builder.DefaultJqlClauseBuilder.addStringCondition(DefaultJqlClauseBuilder.java:928) at com.atlassian.jira.jql.builder.DefaultJqlClauseBuilder.issue(DefaultJqlClauseBuilder.java:595) at com.atlassian.greenhopper.service.timetracking.TimeTrackingHistoryServiceImpl.getTimeTrackingHistory(TimeTrackingHistoryServiceImpl.java:44) at com.atlassian.greenhopper.web.rapid.chart.SprintBurndownModelFactory.getScopeChangeModelDataForSprint(SprintBurndownModelFactory.java:225) at com.atlassian.greenhopper.web.rapid.chart.SprintBurndownModelFactory.getScopeChangeBurndownModel(SprintBurndownModelFactory.java:140) at com.atlassian.greenhopper.web.rapid.chart.SprintBurndownModelFactory.getScopeChangeBurndownModel(SprintBurndownModelFactory.java:129) at com.atlassian.greenhopper.web.rapid.chart.RapidChartResource$3.call(RapidChartResource.java:153) at com.atlassian.greenhopper.web.rapid.chart.RapidChartResource$3.call(RapidChartResource.java:143) at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:42) at com.atlassian.greenhopper.web.AbstractResource.createResponse(AbstractResource.java:100) at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:81) at com.atlassian.greenhopper.web.rapid.chart.RapidChartResource.getScopeChangeBurndownChart(RapidChartResource.java:142) at sun.reflect.GeneratedMethodAccessor1626.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606)
Notes
The code that generates the sprint history does not handle the case where:
- no issues are in the sprint history, AND
- the board is configured to use Time Tracking
Workaround
Disable Time Tracking in the board's Estimation configuration.
If you're seeing this error message attributed to "anonymous" user access, then it is likely because anonymous users are trying to access sprint reports for which they have no visible issues to see. If you can restriction anonymous access, you'll get fewer of these error messages. Please refer to the JIRA Admin Helper to verify permission access to projects.
- relates to
-
-
- Closed
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[JSWSERVER-11484] IllegalArgumentException: clauseValues is empty when accessing sprint reports
Ryan O Sullivan
added a comment - As I said, we use the time tracking for reporting on sprint burndown and also to support external reporting.
I would query why this is only seen as affecting 25% of the user population.
Time tracking is a key function in JIRA and JIRA agile
also what does a developer effort of S mean (small or significant?)
how would burndown work without time tracking? story points ?
Did the new reporting cause this issue?
Ryan O Sullivan
added a comment - As I said, we use the time tracking for reporting on sprint burndown and also to support external reporting.
I would query why this is only seen as affecting 25% of the user population.
Time tracking is a key function in JIRA and JIRA agile
also what does a developer effort of S mean (small or significant?)
how would burndown work without time tracking? story points ?
Did the new reporting cause this issue? Ryan O Sullivan
added a comment - As I said, we use the time tracking for reporting on sprint burndown and also to support external reporting.
I would query why this is only seen as affecting 25% of the user population.
Time tracking is a key function in JIRA and JIRA agile
also what does a developer effort of S mean (small or significant?)
how would burndown work without time tracking? story points ?
Did the new reporting cause this issue?
Ryan O Sullivan
added a comment - As I said, we use the time tracking for reporting on sprint burndown and also to support external reporting.
I would query why this is only seen as affecting 25% of the user population.
Time tracking is a key function in JIRA and JIRA agile
also what does a developer effort of S mean (small or significant?)
how would burndown work without time tracking? story points ?
Did the new reporting cause this issue? Ryan O Sullivan
added a comment - please advise if this is set for a fix Ryan O Sullivan
added a comment - Hit this error when updating from 6.4 to 6.7. this will block any upgrade at my end , disabling time tracking is no valid workaround, we depend on worklogs for burndown and reporting of time
Ryan O Sullivan
added a comment - Hit this error when updating from 6.4 to 6.7. this will block any upgrade at my end , disabling time tracking is no valid workaround, we depend on worklogs for burndown and reporting of time
glad to see this is almost resolved, i will be happy to try it when its released