Ending a sprint and incomplete stories are moved into a future sprint from a different board

[Philippe Robichaud]

In the last 2 sprints, we are encounting an annoying situation with our scrum boards.

Let's say we want to close sprint 999 on "Red" scrum board which contains story A, B and C. Story A and B are completed but not story C. Once we end sprint 999, story C gets added to sprint 1 on a completely different board (let's call it "Blue board"). How can this happen?

I know in the documentation it is written incomplete stories could either be moved in the backlog or in the next plan sprint once we end sprints. But in our case, it does not a appear in the backlog (or next plan sprint) of expected board but on a different board.

Thanks for your help!

[Alan Corey]

Having a similar issue, did you ever figure this out?

[Philippe Robichaud]

Sorry Alan, we didn't.

[Nic Brough -Adaptavist-]

The question about the query still stands - there's something wrong there.

[Nic Brough -Adaptavist-]

Simple answer - blue board's definition includes story C after sprint 999 ends.

[Philippe Robichaud]

Thanks Nic but both board filters query are almost the same. The one and only one difference in the where clause is with one custom field. In the Red board, for the custom field "colour", we look for "color = red" and in the Blue board, we look for "color = blue". And finally, the color custom field value for story C has always been "red".

Other than the board filter query, what are you referring to when you mention the board's definition?

Thanks.

[Nic Brough -Adaptavist-]

No, it's definitely something in the query that the board is using. The baseline query though, not the quick filters or swimlanes.