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

[Lujain Aljaafari]

We're restructuring a Jira Cloud instance (mostly company-managed projects) on the Standard plan, now on the new "Spaces" experience. We want to organize work around a handful of business domains, each containing several teams, plus a program/leadership view spanning all of them.

What I've tried in a test project: created multiple boards in one space and scoped each with a board filter plus Components per team. It works, but tagging every item and hand-filtering each board feels manual and hard to sustain — and cross-team work (items spanning two teams, parent/child across teams) doesn't fit cleanly.

Questions:

1. For one space with several teams, what's the recommended pattern in the new Jira experience — components + filtered boards, one project per team, or something else?

2. How are people handling cross-team items that don't belong to a single board?

3. For genuine program-level rollups across many teams, is Premium / Plans (Advanced Roadmaps) effectively required, or is there a sustainable Standard-plan approach?

4. Any pitfalls migrating existing work into this structure without breaking parent/child links?

Thanks!