Showing agile stories across multiple teams | Adobe Higher Education
Skip to main content
M
MartinAn5
January 30, 2025
質問

Showing agile stories across multiple teams

  • January 30, 2025
  • 2 の返信
  • 413 ビュー

Hi,

Is there a way to create a story in a team, let's say Team 1 (designers) and Team 2 (copy-writers), and then having that same story shown in another team, let's say Team 3 (managers), so that the managers from Team 3, can see the opportunities for cross-team optimizations?

I hope this made sense, else let me know, and I'll try to re-phraze it to the best of my abilities.

2 の返信

Madalyn_Destafney
Community Advisor
Madalyn_DestafneyCommunity Advisor
Community Advisor
January 31, 2025

I believe you'd either have to assign the 3 teams to the same objects in the backlog/stories that you'd want to appear for all 3 teams, or if you don't to cause confusion there, create an issue or task report (whatever you assign as Stories) to pull in all stories from across the 3 teams, grouped by team, so you can see what's on each team's plate. You could use 'assignment team' filter for pulling in the 3 teams you want, then 'story points' or 'iteration' is not blank to pull in stories and nothing else assigned to those teams. 
Just a couple initial thoughts!

If this helped you, please mark correct to help others : )
    M
    MartinAn5作成者
    February 6, 2025

    Hi Madalyn!

    I tried to assign the 3 teams to the same object, but it only showed up in the initial team, where the object was created. It did work with a report, though that really doesn't give the effect I want.

    I will try to do a similiar setup, but using Projects instead, and see what that will end up looking like 😄

     

     

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    September 1, 2025

    @martinan5 just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

    Kautuk Sahni
    契約条件Accessibility statement

    Loading footer...