Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Creating a cross-teams release burndown chart in Jira with Great Gadgets app

Do you have a large release that spreads across multiple projects or multiple teams and you don’t have a good way for tracking it and for making a picture about the overall progress?

With Great Gadgets app for Jira you can solve this quickly. This app offers a Release Burndown/Burnup Chart dashboard gadget that you can use to generate a cross-projects or cross-teams release burndown/burnup in a few steps. The gadget uses the issues from a specified Jira filter as project scope and allows you to specify the release start / end dates. You can choose to display the chart by story points, issue count, original time estimate or by any other numerical custom field defined in your Jira instance and you can also include the issue sub-tasks in the calculation. Optionally, you can choose to display a forecast line that predicts the release ETA and milestones.

Assuming that you already have Atlassian Jira in-place, follow these steps to configure and display the Release Burnup Burndown Chart gadget:

  • Make sure that you have the latest version of Great Gadgets installed in your Jira instance. If not, you can install the app from Atlassian Marketplace.
  • Create a new filter in Jira (or use an existing one) that includes the Jira issues (tasks, stories, defects, etc) from the release (from all the projects/teams) that you want to track. Make sure to include the sub-tasks in this filter if you want the gadget to also consider the sub-tasks. Share this filter with your project members or the people that are going to visualize the chart.
  • Decide on which Jira dashboard you want to add the Release Burnup Burndown Chart gadget. Create a new Jira dashboard or choose an existing one.
  • Add the Release Burnup Burndown Chart gadget to your Jira dashboard.
  • Configure the gadget. At Release Issue Filter, enter the filter that you created before. As you can see, the Intervals of length is configurable and you can choose to calculate by Story Points, Issue Count, Original Time Estimate or by any other numerical custom field.
  • Select which series (lines) to be displayed in the chart.
  • In case you selected a forecast line, select the velocity calculation method at Forecast based on.

That’s all! Click Save. The gadget now displays the cross-teams burndown/burnup chart on your Jira Dashboard.

If you have further questions or suggestions, don’t hesitate to contact


Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 13, 2021

Hi @Danut M _StonikByte_ 

Thanks for the information!  Regarding the "ideal burndown" values, is that always a straight line on this chart, or is it segmented to account for changes in scope over time (which then change the end-point forecast)?

Kind regards,

Like Danut M _StonikByte_ likes this
Danut M _StonikByte_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 16, 2021

Hi @Bill Sheboy 

There is an option in gadget settings to configure where the "ideal burndown" starts from. If you set "Calculate the ideal series based on initial scope" the "ideal burndown" will be a always a straight line that starts from the initial value of the scope, as it was a the start of the release (in day 0). But if you set "Calculate the ideal series based on current scope" then the "ideal burndown" will start from the current (latest) value of the scope series. And yes, the forecast end-point is impacted by the scope changes.



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events