Bug in Sprint Burndown Chart
As a user I want the rendering of the burn-down chart to be reliable -- failing that, to give me a hint as to why it's failing -- so I don't have to go figure out what's wrong with my project.
Here's from the catalina.out:
FATAL AHttpServlet GET failed: scrum.server.sprint.SprintBurndownChartServlet ->
java.lang.IllegalArgumentException: snapshots.isEmpty()
at scrum.server.common.BurndownChart.createSprintBurndownChartDataset(BurndownChart.java:212)
at scrum.server.common.BurndownChart.writeSprintBurndownChart(BurndownChart.java:125)
at scrum.server.common.BurndownChart.writeSprintBurndownChart(BurndownChart.java:93)
at scrum.server.common.BurndownChart.writeSprintBurndownChart(BurndownChart.java:80)
at scrum.server.sprint.SprintBurndownChartServlet.onRequest(SprintBurndownChartServlet.java:31)
at scrum.server.common.AHttpServlet.doGet(AHttpServlet.java:33)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:636)
| app:kunagi > session:dcuddihy
Statement from Kunagi Team
This bug occurs, when the current sprint has wrong dates set.
Status
Issue is closed for Release 0.14.