Summary

Currently when completing a Sprint that has many (Tested with 350 and 184) uncompleted issues, and choose to move the uncompleted issues to a future Sprint, the issues are first moved to Backlog and after about 30 seconds are moved to the selected Sprint.

On a vanilla instance, we were able to reproduce this with 3500 issues. However, on production instances it may be recreated with hundreds of issues to be moved to the next Sprint.

This might confuse the customers that the issues are moved to Backlog.

Steps to Reproduce

1. Create a board and 2 sprints
2. Create 3500 issues in one sprint
3. Start and complete sprint (keep all issues open)
4. Select option to move issues to the other sprint.

Expected Results

All issues are processed and moved to the other sprint.

Actual Results

Operation times out and we get this error:

Only part of the issues are moved to the other sprint.
Despite the timeout in the UI, the operation continues in the background and eventually all issues are moved to the other sprint.

Notes

We can see different number of issues causing this problem depending on the issues. Simple issues on clean instance on new projects seem to require 3500+ issues to cause this problem.

The operation can either be made faster to avoid the timeout (which might not be possible due to various customizations) or transformed into a long-running task with a progress bar to better reflect the progress to the end user.

Workaround

First bulk move some tickets to the other sprint and then complete it.

Suggested Solution

Improve performance