Aggregate all stories and issues into one united sprint view?

[Mariko Davidson]

Hi there,

We currently have 6 different team projects with their own scrum boards, all using different sprint names. I am trying to create a "portfolio" scrum board that pulls in all the sprint tickets under one sprint. I've been able to create a board that does that BUT it still breaks up the tickets by project team.

Is there a way to aggregate them all in under one sprint, without the team project sprint name dividers (above, e.g. "BP Sprint 21," "DP Sprint 38," etc) so we can review ALL the tickets being worked on at the company level in one sprint?

Once this is achieved, can we move tickets up and down the "portfolio" queue if we want to change the level of priority of the ticket (at the company level)? 

[Danut M _StonikByte_]

Hi @Mariko Davidson,

Why you actually need this aggregation? 

If you want this for tracking the global progress in form of burndown chart, velocity chart, etc, be aware that you can do this without being necessary to put all the items in one sprint. 

Have a look over this article from our blog: How to track multi-team or scaled-agile projects (such as SAFe®) in Jira with Great Gadgets app 

As you will see, with our Great Gadgets app you can have burn-down chart, velocity chart etc at the global level.

If you have any questions, don't hesitate to contact us at support@stonikbyte.com.

Regards,

Danut Manda

[Trudy Claspill]

Hello @Mariko Davidson 

Welcome to the Atlassian community.

No, you can't do that. An issue can be assigned to one and only one Active or Future sprint at a time. It doesn't make sense for an issue to be assigned to multiple sprints.

Prioritization of the issues, in the manner of dragging and dropping them up and down the lists in the Backlog or Sprints, is tracked at a global level rather than a board level. If you did have a board that displayed all the issues from these separate teams, and if you started dragging and dropping issues to change the order in which they were displayed, those changes would be reflected in all the other boards where those issues are displayed.

You would need to use a separate method for tracking the "priority" of the work at a company level. You could, for instance, use the Advanced Roadmaps functionality available in the Premium subscription to define another issue type (Initiative) which you arrange based on the priorities of the company. You could make Epics children of the Initiatives, and have the teams organize their work into Epics that align with the company Initiatives.

It sounds like what you are looking to implement is portfolio management. You can do that with the built-in Advanced Roadmaps feature that is available with the Premium subscription. You should spend some time reviewing the capabilities of that feature set.

https://www.atlassian.com/software/jira/features/roadmaps?tab=advanced

https://www.atlassian.com/software/jira/guides/advanced-roadmaps/overview#what-are-advanced-roadmaps

https://support.atlassian.com/jira-software-cloud/docs/plan-and-view-cross-project-work-with-advanced-roadmaps/

[Laurie Sciutti]

hello @Mariko Davidson ~ you can only list an issue in one sprint so if you are aggregating and need these in the same sprint, you'll need to create that new sprint and move those issues into the new sprint.