Issue Summary

A race condition exists in Jira Software where more than one active sprint can exist at the same time when parallel sprints is disabled. This can happen when requests to make a sprint active is sent at the same time.

Steps to Reproduce

1. Install Jira software with a scrum project set up
2. Ensure that there are no sprints currently active
3. Create two sprints (say; “Test 1”, and “Test 2”)
4. Use a script or tool like Burp Suite to send the appropriate call to <base_url>/rest/greenhopper/1.0/sprint/{sprint_id}/start for both id’s of the sprints

A sample script can be found as an attachment. If using this script:

1. Edit the above script to update the BASE_URL, ADMIN_USERNAME, ADMIN_PASSWORD variables with the correct details for your Jira instance.
2. Edit the above script and update the variable SPRINT_IDS with the sprint IDs
3. Edit the above script and update the SPRINT_DATA variable with the id (sprint ID) values, and the originBoardId (board ID)

Using the <base_url>/rest/agile/1.0/sprint/{sprint_id}/start endpoint has the same outcome.

Expected Results

Only one sprint should be marked as active

Actual Results

Both sprints are shown as being active when only one should be

Workaround

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