Skip to end of banner
Go to start of banner

AR - FAQ

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Contents

1. I have Project Burnup Chart 1.X installed. How do I upgrade to a new version?

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

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

You can also refer to Atlassian documentation:

2. The Burnup gadget is not rendered after the 2.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.

3. I get a warning in the chart, what should I do?

Don't panic. (smile) 
Warnings are generated to help you identify cases when chart's data might show not the actual picture. For instance, when an issue is not estimated or when a ticket is resolved outside of the sprint and is not marked as a duplicate or clone. The tickets in the Warnings tab are not in included into the chart calculations, so to ensure the chart's accuracy, click the issue in the warning and fill out the necessary fields.

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

For you to have data on the Project Burnup Chart, ensure that you have at least one sprint on the board that you have selected for the report.

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

Quite easy. You create and configure a SCRUM board that would display tickets that you want to track on the report. The board can contain tickets from one or 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 2.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.

In this case you might want to do the following checks:

  • ensure that all tickets are in their up-to-date status
  • analyze the estimates and adjust them if needed
  • analyze the progress with your team to identify the cause of delay
  • remove some tickets from the sprint or version

7. How do warnings work?

In Project Burnup Chart 2.0 we have introduced Warnings functionality. It will save you time and will help quickly identify tickets that require your attention.

Now 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.

The tickets in the warnings are not included in the chart, so that it displays only "pre-checked" data. We recommend that you take a look at each "rejected" issue that got into the Warnings tab.

8. I have selected a start date but the data on the chart is starting from a different date. Why?

This can happen if you select a start date that is in the middle of the sprint. When you do so, the report autocorrects the start date to the beginning of that sprint in order for you to have the most accurate data grouped by sprints.

9. How do you treat parallel sprints?

We treat parallel sprints in the same way, thus you will see a point for each sprint. if they are one above the other, it means that those sprints end in the same day.

10. I have a question that's not on this list.

If you have a suggestion or a request, we would be happy to hear it! You can connect with us through our customer portal.

  • No labels