Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to obtain an Epic Burndown with Epics belonging to different Projects?


I have tried to create an Epic "E" in project "A".

Then, I have created 2 issues in the project A belonging to the Epic E.

Finally, I have created an issue in the project "B" belonging to the Epic E.

However, in the Epic Burndown, I only see the issues belonging to the project A and not the one linked to project B.

Could you please help me?



1 answer

1 accepted

2 votes
Answer accepted

Hi @Daniele Mannelli,

I played with this a bit in my test system, but I didn't have the full set up of issues to get accurate results and I ran out of time for setting it up.'s what I was trying, perhaps you can give it a shot and let me know if it works...

  • In the left nave, select "Issues and Filters"
  • Click "Search Issues" and create a new filter in the Advanced line starting with "project in (PROJECT_A, PROJECT_B)" and save it. (I suggest starting with that by itself before tying to limit the results...this will get every issue from both projects.
  • Go to "Dashboards" from the left nav and select "View All Dashboards."
  • Go into one of your two projects, and create a new board, and use a Scrum board.
  • When prompted, select "Create from existing filter"
  • Give the board a name, select your new filter with both projects, and pick a place for it to live. (I put mine in my personal space so I don;t get it confused with other projects)
  • Once done, go into the space where the new board lives and open it.
    • Boards1.JPG
  • Click "Reports" from the left nav and select "Epic Burndown."

If I'm right this will use all the issues in your saved filter from both projects and create a burndown for your Epic A and Epic B. Once you verify it you can create other filters and boards to generate other types of reports, parse data from multiple projects, etc. 

It's a bit clunky, but should get you started without having to write extensive scripts or use add-ons. 


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events