Recommended structure for multi-team, program-level management in the new Jira experience.

Hi @Lujain Aljaafari 

You need Pans for this, this comes with a Premium or Enterprise subscription.

IF you are on a Standard subscription you will need a 3rd party marketplace app for this, like;

• Structure
• BigPicture
• etc..

Hi @Lujain Aljaafari and welcome to the Community!

You've already hit the real limitation: components + board filters technically work, but they put the burden on tagging and hand-filtering, and they break down the moment work spans two teams or parent/child links cross team boundaries. A few patterns that tend to hold up better:

• For several teams in one space, project-or team-scoped boards driven by saved JQL filters (rather than components) age better, because membership follows query logic instead of manual tags. Atlassian Teams can help you slice cross-team views without re-tagging every issue.
• For cross-team items, lean on issue links and a shared parent hierarchy rather than trying to make one board "own" them, then surface them through a filter-based view rather than a single board.
• For genuine program-level rollups across many teams, native Standard-plan tooling will stay manual. Premium/Plans (Advanced Roadmaps) is effectively the line where cross-project hierarchy and rollups become sustainable; on Standard you can approximate it, but expect the upkeep you're already feeling.
• On migration: the main pitfall is broken parent/child links. Map your hierarchy before you move anything and do the re-parenting via a controlled bulk/CSV step so links are preserved rather than recreated by hand.

If the program/leadership view you're describing is heading toward a Scaled Agile (SAFe) operating model, it may be worth looking at a layer purpose-built for multi-team, program-level structure. And just in full disclosure, I work on Agile Hive. Here are a few points I think are relevant here in Agile Hive:

• Enforces a full Portfolio → Solution → ART → Team hierarchy in the data model, so cross-team parent/child relationships are first-class rather than something you maintain with components
• Native Planning Interval (PI) execution and a planning board built for multi-team coordination and dependency management across an ART
• Program- and portfolio-level rollups and executive dashboards that read from live Jira data, which is the leadership view you're trying to assemble manually today
• Lean Portfolio Management (funded epics and strategy-to-delivery traceability) inside Jira
• Stays entirely inside Jira with no separate system of record, so you're not adding another tool to reconcile

More detail at https://www.agile-hive.com, and there's a free trial on the Atlassian Marketplace if you want to test the structure against your domains-and-teams setup.

Hope this helps, best of luck, and again, welcome!


Joshua
Content Writer & US Representative
Agile Hive and Aura Apps (products of Seibert Group GmbH)