Deleting a Scrum Board with more than 50 completed sprints it does not notify about active sprints

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 10.0.0
    • Affects Version/s: 9.7.0, 9.12.9, 9.12.11, 9.17.1
    • Component/s: AgileBoard, Sprint
    • 9.07
    • 2
    • Severity 3 - Minor
    • 5

      Issue Summary

      From Jira Software 9.7 a feature exists to warn of active sprints when deleting a scrum board. If however the scrum board has more than 50 completed sprints deleting the board will display no warning of active sprints present due to the limitation in the sprint query used.

      Steps to Reproduce

      1. Create a Scrum board for a project
      2. Create at least 50 sprints and complete them, there needs to be at least 50 'closed' sprints
      3. Create a new active sprint
      4. Attempt to delete the board

      Expected Results

      A warning in the delete board action popup showing the board's active sprints.

      Actual Results

      No warning of active sprints is shown.
      This is due to the query used to find active sprints being the REST API endpoint to show a board's sprints. For example

      https://jira-url.domain/rest/agile/1.0/board/111/sprint?_=23456
      

      With no parameters sent we get data of the form

      {
          "maxResults": 50,
          "startAt": 0,
          "isLast": false,
          "values": [
              {
      ...
      

      This shows at most we have 50 returned sprints and when the "isLast" value is "false" the data set is not complete and we have more than 50 sprints. If all the returned sprints show a "state" of "closed" then no warning of active sprints is shown. This is likely as with a large number of sprints the most recent and active will be the 51st or later sprint.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Mateusz Witkowski
            Reporter:
            James Forrester
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: