How do you related multiple Epics to an Atlassian Project for reporting and visibility?

[Andrew Miller]

I am a bit baffled, so I will assume I am missing something important - how does Atlassian capture all of the work (end to end, across multiple departments) related to an Atlassian Project? From my understanding, only a single Jira Epic can be connected to an Atlassian Project ("Where is the work tracked?"). If I have an Atlassian project, where multiple departments are working towards it, and are working on separate team Jira boards, how is this captured if I can only link a single Epic to the Project? 

A Project needs to be able to rollup progress/reporting from multiple Jira boards and multiple Epics. For example, a project involves BA, Dev, UAT, Ops, and CS teams. Each has their own Jira work to track their actions. All of their Epics need to be tied to the overall project. The overall Atlassian Project needs to show overall progress (out of the 5 Epics, roll up the % completion, or stages, or at least see which Epics are effecting the Project). 

Same with reporting. Multiple separate teams should be able to contribute to Project's update, and the Project update should roll up all of their individual updates into a single Project update. 

Rovo tells me this is not possible. Please tell me I'm wrong! Or if my process above is against industry standards, what is the best in class solution for my need? 

[John Funk]

Hi Andrew - Welcome to the Atlassian Community!

An Epic can only be associated with a single project. But the children of Epics can come from multiple projects. If you are on a Story or Task on one project, you can click in the Parent field and link it to an Epic in another project.