Is there any way to link more Epics to the new Projects?

[Torben]

First of all I like the whole renaming of projects to spaces and having now the possibility to actually report on projects. 

The main issue I have for now is, that using the "Where is the work tracked?" I can only link one EPIC to it. Usually we have projects that take longer than one iteration and might also span across teams and services. So having the possibility to link multiple Epics is essential.

Any idea on either a better way or when this will be possible? I am open for suggestions ;-)

[Ali Umut Terzi · Accepted solution]

Hi @Torben ! 👋

That’s a great question — and you’re not alone on this one 🙂

This is by design — Jira currently treats “Project” as a container level entity above a single Epic, not a grouping of multiple Epics.

If your real-world projects span across several Epics (which is quite common), there are a few ways to handle this effectively:

1. 🧩 Use an Initiative or higher-level issue type
   If you have Advanced Roadmaps (Plans) enabled (Jira Premium Plan), you can create an Initiative issue type and link multiple Epics under it using the hierarchy configuration.
   → That way, your “Project” view can roll up several Epics naturally.
2. 🔗 Use issue links instead of the Project field
   You can manually link several Epics to one “Project” issue using a custom link type, e.g. “is part of project”.
   This lets you report across all linked Epics using filters or dashboard gadgets.
   
   
   Create a filter like:

          issue in linkedIssues("ABC-123", "relates to")

          [This filter shows all issues that are linked to ABC-123 with the “relates to” link type.]

I had a similar situation — multiple Epics from different teams contributing to one shared project.

We solved it by creating a dedicated parent issue type (Initiative) in Advanced Roadmaps and connecting all related Epics under it.

That approach worked perfectly for cross-team visibility while keeping Jira’s hierarchy clean.

Hope this helps! 🙂

[Torben]

Thanks @Ali Umut Terzi 

This did clarify the situation and helped in that sense. Upgrading to Premium because of this is not yet an option for us.

I expect this design decision is down to the MVP state of this feature and not long term. I hoped I could avoid maintaining filters for each project, but if I need to make them anyway, I probably continue doing project reports in confluence.

Lets see where this goes...