Issues that belong to multiple Agile Boards

[Chris Kast]

Was hoping to get some feedback on this issue. Here's the scenario: we have single scrum board that tracks our current project. The filter is just a single project. We have developers who like the "view" of the scrum board and want to create their own personal board that includes not only issues from the current project but other projects we have as well.

The problem with this is that because sprints are a property of the issue and not the board, when there's overlap between 2 or more boards' filters, things get a little wonky in the sense sprints that meant for Board A start showing up on Board B (and visa versa). Can anyone suggest a workaround for this?

[Nic Brough -Adaptavist- · Accepted solution]

Sprints do sort of belong to boards, that's why they're appearing when you've got more than one board for an issue.

The simple answer is to not use scrum boards for anything other than the scrums where you'll be executing sprints.  Try to keep your scrum boards for the sprints, and get your developers to use Kanban boards instead - these don't care about sprints, so things won't go wonky (just ask the devs not to click "release")

[Chris Kast]

Thanks, Nic! I never thought of using Kanban boards. I think this is exactly what we need.