java.lang.IllegalStateException: Issue ABC-123 has multiple active or future sprints

Atlassian JIRA | David Currie [Atlassian] | 3 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    h3. Summary Attempting to edit an issue presents with the error "Issue has multiple acive or future sprints" [sic]. This prevents saving the changes to the issue. The following may appear in the _atlassian-greenhopper.log_: {code:borderStyle=solid} 2015-12-03 11:08:20,373 http-bio-8080-exec-1099 ERROR lgodbole 668x100203x7 1ou4znq 10.0.0.3,127.0.0.1 /rest/greenhopper/1.0/xboard/issue/details.json [web.rapid.issue.IssueResource] Unable to complete GreenHopper REST method java.lang.IllegalStateException: Issue ABC-123 has multiple active or future sprints at com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl$SprintFilterFunction.apply(SprintIssueServiceImpl.java:381) at com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl$SprintFilterFunction.apply(SprintIssueServiceImpl.java:364) at com.atlassian.greenhopper.service.ServiceOutcomes.map(ServiceOutcomes.java:38) at com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl.getActiveOrFutureSprintForIssue(SprintIssueServiceImpl.java:235) at com.atlassian.greenhopper.web.rapid.issue.IssueResource$1.call(IssueResource.java:127) at com.atlassian.greenhopper.web.rapid.issue.IssueResource$1.call(IssueResource.java:106) at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:42) at com.atlassian.greenhopper.web.AbstractResource.createResponse(AbstractResource.java:115) at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:96) at com.atlassian.greenhopper.web.rapid.issue.IssueResource.getPageData(IssueResource.java:105) at sun.reflect.GeneratedMethodAccessor2080.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) {code} h3. Steps to Reproduce # Restore an instance with a problematic data set (one that has managed to get multiple Sprint fields onto one edit screen in different tabs). # Edit the issue and change the sprint field. # Attempt to save the changes. h3. Expected Results The changes are successfully sent. h3. Actual Results The changes fail to save and the attached error is presented to the user. h3. Notes This is caused by multiple Sprint fields appearing on the edit screen in different tabs. This appears to be caused by an upgrade task. Additionally in earlier versions the spelling of "acive" was incorrect, and has since been updated to "active". h3. Workaround Edit the screen for that project and remove the Sprint field from one of the tabs as per [Defining a Screen|https://confluence.atlassian.com/display/JIRA/Defining+a+Screen#DefiningaScreen-Editingascreen'sdetails]. This will prevent JIRA Agile from displaying this error.

    Atlassian JIRA | 3 years ago | David Currie [Atlassian]
    java.lang.IllegalStateException: Issue ABC-123 has multiple active or future sprints
  2. 0

    h3. Summary Attempting to edit an issue presents with the error "Issue has multiple acive or future sprints" [sic]. This prevents saving the changes to the issue. The following may appear in the _atlassian-greenhopper.log_: {code:borderStyle=solid} 2015-12-03 11:08:20,373 http-bio-8080-exec-1099 ERROR lgodbole 668x100203x7 1ou4znq 10.0.0.3,127.0.0.1 /rest/greenhopper/1.0/xboard/issue/details.json [web.rapid.issue.IssueResource] Unable to complete GreenHopper REST method java.lang.IllegalStateException: Issue ABC-123 has multiple active or future sprints at com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl$SprintFilterFunction.apply(SprintIssueServiceImpl.java:381) at com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl$SprintFilterFunction.apply(SprintIssueServiceImpl.java:364) at com.atlassian.greenhopper.service.ServiceOutcomes.map(ServiceOutcomes.java:38) at com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl.getActiveOrFutureSprintForIssue(SprintIssueServiceImpl.java:235) at com.atlassian.greenhopper.web.rapid.issue.IssueResource$1.call(IssueResource.java:127) at com.atlassian.greenhopper.web.rapid.issue.IssueResource$1.call(IssueResource.java:106) at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:42) at com.atlassian.greenhopper.web.AbstractResource.createResponse(AbstractResource.java:115) at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:96) at com.atlassian.greenhopper.web.rapid.issue.IssueResource.getPageData(IssueResource.java:105) at sun.reflect.GeneratedMethodAccessor2080.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) {code} h3. Steps to Reproduce # Restore an instance with a problematic data set (one that has managed to get multiple Sprint fields onto one edit screen in different tabs). # Edit the issue and change the sprint field. # Attempt to save the changes. h3. Expected Results The changes are successfully sent. h3. Actual Results The changes fail to save and the attached error is presented to the user. h3. Notes This is caused by multiple Sprint fields appearing on the edit screen in different tabs. This appears to be caused by an upgrade task. Additionally in earlier versions the spelling of "acive" was incorrect, and has since been updated to "active". h3. Workaround Edit the screen for that project and remove the Sprint field from one of the tabs as per [Defining a Screen|https://confluence.atlassian.com/display/JIRA/Defining+a+Screen#DefiningaScreen-Editingascreen'sdetails]. This will prevent JIRA Agile from displaying this error.

    Atlassian JIRA | 3 years ago | David Currie [Atlassian]
    java.lang.IllegalStateException: Issue ABC-123 has multiple active or future sprints

    Root Cause Analysis

    1. java.lang.IllegalStateException

      Issue ABC-123 has multiple active or future sprints

      at com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl$SprintFilterFunction.apply()
    2. com.atlassian.greenhopper
      IssueResource.getPageData
      1. com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl$SprintFilterFunction.apply(SprintIssueServiceImpl.java:381)
      2. com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl$SprintFilterFunction.apply(SprintIssueServiceImpl.java:364)
      3. com.atlassian.greenhopper.service.ServiceOutcomes.map(ServiceOutcomes.java:38)
      4. com.atlassian.greenhopper.service.sprint.SprintIssueServiceImpl.getActiveOrFutureSprintForIssue(SprintIssueServiceImpl.java:235)
      5. com.atlassian.greenhopper.web.rapid.issue.IssueResource$1.call(IssueResource.java:127)
      6. com.atlassian.greenhopper.web.rapid.issue.IssueResource$1.call(IssueResource.java:106)
      7. com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:42)
      8. com.atlassian.greenhopper.web.AbstractResource.createResponse(AbstractResource.java:115)
      9. com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:96)
      10. com.atlassian.greenhopper.web.rapid.issue.IssueResource.getPageData(IssueResource.java:105)
      10 frames
    3. Java RT
      Method.invoke
      1. sun.reflect.GeneratedMethodAccessor2080.invoke(Unknown Source)
      2. sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      3. java.lang.reflect.Method.invoke(Method.java:497)
      3 frames
    4. com.atlassian.plugins
      DispatchProviderHelper$ResponseOutInvoker$1.invoke
      1. com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234)
      1 frame