Board insights and issue source

Question

Hi,

I work in a large project where we use Jira cloud. We have several teams with separate boards, yet the sprints are managed centrally. The insights (sprint insights / backlog insights, the feature accessible from board) thus shows stats for ALL issues in the project for a sprint, instead of just one team. Is this possible to change?

It is a way for the teams to get some quick stats, and the overall project metrics are irrelevant in the situation that view is most used.

jenseilertsen · Answer

Yeah I hope so too, and unfortunately it does not sound like that would fit us so well (although it is great to hear that you had a solution in your case :D ).

Case for us is that we have one board "management" where we centrally run and manage the sprints (which are equal for everyone on timing), and then for example "Integration" team have their own board, associating stories to the common sprint. So on their board, they only see their own issues, not for example "UX" team's issues - but the "UX" team issues show up in the insights even if they are not on the board.

So currently, we have 1 "Sprint X" for everyone (which I believe makes most sense, as leadership can look at stats for the overall projects over sprints) - which works for everything but the Insights mechanism. And if we were to have "Sprint X - Integration" and "Sprint X - UX", we would end up with about 30 Sprint Xs hehe

Boldizsár Vermes · Answer

You still can centrally see, manage, start, and complete sprints on a single board, sprints can appear on multiple boards. The only need is to create the sprints on the board where you want to see the backlog insights for the given team. I think, planning and starting a sprint for a team can happen on a board that is dedicated to them (issues already put into other teams' sprints would be just noise here). But if this "solution" is not suitable for you, I can understand it too. I hope Atlassian hears us with different scenarios and way of use of backlog insights :)

jenseilertsen · Answer

Thanks for the response. I believe that this fix may not work as well in our situation as, while we need different boards for the many teams, the sprint are ran centrally. Or is your plan then to centrally create every sprint per team/board? I think that would create quite the chaos given the amount of teams we have.