Problem Definition

Per documentation at Ending a Sprint , when ending a sprint, any incomplete issues should be moved to the next planned sprint if available. Otherwise, the issues should be moved to the backlog.

However, when a project has multiple boards, and a sprint is completed from a board based on a JIRA issue filter, any incomplete issues not visible from that specific board are not moved to the next sprint, and are instead placed in the backlog. Only the incomplete issues visible to that specific board are moved into the next sprint.

To reproduce,

1. Create a new project (e.g. TestProject)
2. Add 4 issues to the project, and assign 2 of them with a Labels value of A, and the other 2 with a Labels value of B
3. Add two sprints (e.g. Sprint #1, and Sprint #2), and place one issue with Labels = A and one issue with Labels = B in each.
4. Create and save a new Issue filter (e.g. Filter A): project = TestProject AND labels = A
5. Create a new board (e.g. Board A) in the project from an existing Saved Filter, using Filter A
6. Start Sprint #1 from any board
7. Complete Sprint #1 from Board A

Results: The incomplete issue visible in Board A was moved to Sprint #2. However, in the default board, we can see the hidden issue was moved into the Backlog instead of Sprint #2.

Suggested Solution

Move all incomplete issues in a sprint, even those not visible in the current Board, to the next sprint when completing the Sprint, assuming there exists a next planned sprint. This will allow for more consistent, predictable behavior.

For additional flexibility, provide the user a choice on where incomplete issues (visible and not visible to the current Board) should go. This is similar to the existing open suggestion: https://jira.atlassian.com/browse/GHS-6421

If this behavior is not currently documented, update the "Ending a Sprint" article to elaborate on this behavior.

Workaround

Avoid completing sprints from a board where issues in the sprint are not visible.