A user in my realm is asking this question. I'm not sure of the wisdom of doing such a thing, but would appreciate any advice that could support or refute such a desire. Thanks, Mike
A board is associated to a filter, and it will show all the issues that are retrieved by the filter associated to it. So, if the filters associated to different boards retrieve the same set of issues, they will be displayed in more than one board.
There's no problem in that, just keep in mind that if the issues that are displayed in more than one board are added to a sprint, the sprint will be also shown in multiple boards, and if you complete the sprint in one board, this will be reflected in all the other boards.
Hope this helps.
I'm assuming that the sprint 'name' would have to be the same across all boards? If one board closes the story, I'm assuming it's closed for all boards. We have had some issues where an issue was in two boards with the same sprint name, and when that issue was closed one boards sprint was sent back to the backlog.
The boards are just views into your issues, so the Sprints you see on a board can exist on multiple boards (the Sprints you see on a board are shown based on the issues retrieved from that filter - if an issue belongs to a Sprint, and that issue is retrieved in the filter for multiple boards, that Sprint will show on multiple boards). So, Sprints are global objects, and the reason the issues were sent back into the backlog on the other board was that it was the same Sprint. It's important to keep this in mind when viewing issues across multiple boards
I'm John Allspaw, co-founder of Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs