Versions Compared

Old Version 3

changes.mady.by.user Admin Adminovich (Deactivated)

Saved on

compared with

New Version 4

changes.mady.by.user Elena Kolesnik

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you already have Project Burnup Chart 1.0 installed and you want to upgrade to 2Burndown report 3.0, uninstall the old version first and then install the new one.

  1. Log into your JIRA Jira as Admin.
  2. From JIRA Jira administration console, click the Manage add-ons link.
  3. Locate Project Burnup ChartLocate the Burndown report, and click the Update button. 

...

2. The

...

Burndown gadget is not rendered after the

...

3.0 upgrade, what should I do?

We changed and renamed the key for the gadget. All you need to do is to uninstall the old version and install the new one.

...

4. I don't see any data on the chart. What can I do?

See the following tips and tricks for the best results in your Agile Reporting:

Expand
titleBurnup / burndown report

For you to have a meaningful data on the

...

Burndown gadget, check on the following items:

  • You have at least 1 active sprint to filter by SCRUM board
  • There are at least 5 days between the start and end dates for the report
  • Deviation percentage is not greater than 30%. If it's very low (10% for instance), then your team has to operate in very tight boundaries and will often fail to be on track even though their progress might be good enough. If you set the deviation for more than 30%, reporting starts to lose its purpose as a very significant delay will not ring the bell, you will not get the warnings, while the work delay might be an alarming one.
  • You check the Warnings tab from time to time and process tickets there. The tickets shown in the Warnings tab are not included into the chart calculations, and to see the accurate picture on the chart, you might want to triage those tickets first.
Expand
titleCommitted vs Completed Gadget

For you to have a meaningful data on the Committed vs Completed Gadget, check on the following items:

  • You have at least 1 completed sprints to filter by the SCRUM board
  • You check the Warnings tab from time to time and triage tickets from there. The tickets shown in the Warnings tab are not included into the chart calculations, and thus in order to see the accurate picture on the chart, you might want to triage those tickets first.
Expand
titleRelease Prediction Chart

For you to have a meaningful data on the Release Prediction Chart check on the following items:

  • You have at least 2 completed sprints on the SCRUM board
  • You check the Warnings tab from time to time and triage tickets from there. The tickets shown in the Warnings tab are not included into the chart calculations, and thus in order to see the accurate picture on the chart, you might want to triage those tickets first.

5. How can I display data for one project? How can I display data for several projects?

...

6. The previous version had a danger zone on the chart. Where can I find it in the new version?

Project Burnup Chart 2Burndown report 3.0 now has the deviation lines where you define which deviation from the estimates you consider to be a norm. The Deviation (late) line has a danger zone below. If the Sprint actuals line is below the Deviation (late) line (thus entering the highlighted danger zone on the chart),  the progress is too slow.

...

7. How do warnings work?

In Project Burnup Chart 2Burnupdown report 3.0 we have introduced Warnings functionality is available. It will save you time and will help quickly identify tickets that require your attention.

Now we We generate warnings when

  • The ticket is not estimated and thus might affect the chart's accuracy
  • The ticket is resolved outside of the sprint and is not marked as a duplicate or clone.

...