Issue Summary

Sprints from other boards will appear in the backlog if a sub-task level issue returned by the board filter inherits that sprint value from its parent issue, even if the parent issue itself isn't in scope.

This makes the sprint appear empty, because the sub-task can't be displayed in the backlog without the parent.

Sub-task level issues have only become visible on the backlog with the enhanced board and backlog update. This behaviour is only seen in the enhanced backlog.

Examples:

• In a future sprint the parent issue is in a completed status but the subtask is not

• The board filter excludes the parent based on an issue field value that isn't shared by the child issue, like Label

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

1. Create a sprint on board A
2. Add a story-level issue to the sprint and give it a label
3. Give the issue a sub-task and don't give it the same label
4. On board B, set the board filter so that it will include the sub-task but exclude the label on the parent issue (eg. "project = A AND (labels is empty OR labels != "Label")" )

Expected Results

If no story-level issue in the sprint is returned by the board filter, and the sprint belongs to a different board, the sprint is not shown.

Actual Results

The sprint will appear on all other boards where the filter criteria include the sub-task, but the sub-task isn't displayed and the sprint looks empty.

Workaround

Workarounds currently would need to be considered based on the individual boards, and why the sub-task is valid to show in the backlog but the parent issue isn't.

For cases where the board filter excludes the parent issue based on field value the main options are:

• Change the filter to include the parent or exclude the sub-task
• Match the sub-task field value to the value on the parent.

For future sprints that are appearing because the sub-task isn't completed, but the parent task is, consider the accuracy of the issue statuses and inclusion in the sprint. Possible solutions to make the sprint display correctly:

• Remove the parent issue from the sprint. A completed issue shouldn't need to be in a future sprint.
• Transition the sub-task to a completed status. If the parent issue is complete, the work described in the sub-task should be as well.
• Start and complete the sprint. If the sprint is valid and work is in progress, but for some reason the sprint wasn't started, start it and complete it as normal.
• Delete the sprint. Only if the sprint was created by mistake or is invalid, and no historical or report information on it needs to be retained. Deleting a sprint is permanent and removes it from all boards.