Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-16588

When closing a sprint via the REST API, you should be able to indicate where to place the incomplete issues in the sprint

    • 5
    • 6
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      When you close a sprint in the web interface, and it contains issues that were not completed, then you are prompted to then tell Jira Software where to place those incomplete issues (ie. to the backlog, into an existing future planned sprint, or possibly create a new sprint to add these issues to that).
      However with the current REST API, you can not use any parameter into the endpoint

      /rest/agile/1.0/sprint/{sprintId}

      that would allow you to do this when closing the sprint via REST call.  See https://developer.atlassian.com/cloud/jira/software/rest/#api-sprint-sprintId-put for complete parameters that are valid for this call.

      Suggested Solution

      It would be helpful if the REST API was updated for Agile/Software to include this as a possible option

      Why this is important

      It would be helpful for integration/automations that handle sprint management to be able to do this same function that end users using the web gui can perform.

            [JSWCLOUD-16588] When closing a sprint via the REST API, you should be able to indicate where to place the incomplete issues in the sprint

            SET Analytics Bot made changes -
            Support reference count Original: 5 New: 6
            SET Analytics Bot made changes -
            UIS Original: 4 New: 5
            SET Analytics Bot made changes -
            UIS Original: 2 New: 4
            SET Analytics Bot made changes -
            Support reference count Original: 4 New: 5
            SET Analytics Bot made changes -
            UIS Original: 1 New: 2
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            Support reference count New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 2

              Unassigned Unassigned
              aheinzer Andy Heinzer
              Votes:
              38 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated: