-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
6.3.5
-
None
-
6.03
-
Problem
When deleting a future sprint from Plan Mode, the user sees an error message "Internal Server Error" (see screenshot).
There is also a stacktrace in the logs:
[INFO] [talledLocalContainer] 2013-11-27 10:59:21,320 http-2990-2 ERROR admin 659x741x1 13rnn60 0:0:0:0:0:0:0:1%0 /rest/greenhopper/1.0/sprint/31 [web.rapid.sprint.SprintResource] Unable to complete GreenHopper REST method [INFO] [talledLocalContainer] java.lang.NullPointerException [INFO] [talledLocalContainer] at com.atlassian.greenhopper.util.VersionKit.version(VersionKit.java:279) [INFO] [talledLocalContainer] at com.atlassian.greenhopper.entity.remotelink.NoopRemoteServiceLinkAdapter.deleteAll(NoopRemoteServiceLinkAdapter.java:59) [INFO] [talledLocalContainer] at com.atlassian.greenhopper.service.sprint.RemoteSprintLinkService.removeAllRemoteSprintLinks(RemoteSprintLinkService.java:220) [INFO] [talledLocalContainer] at com.atlassian.greenhopper.service.sprint.SprintServiceImpl.deleteSprint(SprintServiceImpl.java:148) [INFO] [talledLocalContainer] at com.atlassian.greenhopper.web.rapid.sprint.SprintResource$4.call(SprintResource.java:203) [INFO] [talledLocalContainer] at com.atlassian.greenhopper.web.rapid.sprint.SprintResource$4.call(SprintResource.java:174)
This only affects JIRA versions prior to 6.1.1.
Affect
The sprint is still removed. The error message will disappear if the page is refreshed.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-10120] Removing a future sprint shows an Internal Server Error
markdw I'm glad we were able to find a quick resolution. It is strange though that you are seeing this bug in JIRA 6.1.1. I tested this manually and I cannot reproduce the same problem.
MarkW
added a comment - I just submitted a support issue and hercules found this for me. I must say that it is incorrect stating that it only affects JIRA versions prior to 6.1.1. I encountered this error when testing Agile 6.3.5 in JIRA 6.1.1.
I eagerly await when this fix is pushed out. 
MarkW
added a comment - I just submitted a support issue and hercules found this for me. I must say that it is incorrect stating that it only affects JIRA versions prior to 6.1.1. I encountered this error when testing Agile 6.3.5 in JIRA 6.1.1.
I eagerly await when this fix is pushed out.
Yeah, it's very weird. It happens on both platforms that I have JIRA 6.1.1 and Agile 6.3.5. Thanks!