First you need to add this report After you have installed Agile Reports, you can add its gadgets to your dashboard. To do that, click Add new gadget.  In the Add new gadget dialog, click Load all gadgets. Search for the Program Predictability Measure report and add it to your dashboard.

To see more instructions about adding a gadget to your dashboard see Atlassian documentation.

Configuring the report

To configure the report, fill out the fields in its settings (see fields description below).

Image Removed

...

This is a standard procedure and you can find details and instructions in Atlassian documentation.

Configuring the report

To configure the report, perform the following operations:

1. Ensure you are good on the prerequisites;
2. Fill out the fields in the gadget settings.

Image Added

Prerequisites

For you to have data on the report, check on the following prerequisites. This is critically important because if your setup is not what SAFe and gadget expects, you will not get proper or any data.

1. Agile Release Train field exists and is properly set up
   
   
   1. Single select Jira custom field.
   2. This custom field must be created and configured in Jira, not by a 3rd party plugin.
   3. It has this exact name "Agile Release Train".
   4. It has options configured.
   5. This custom field is configured for the projects that you want to report on or is global (recommended).
   6. You have tickets that have this ART selected.
      
      
2. Program Increments are set up for each project in the ART
   SAFe often uses Jira's FixVersion field for the Program Increments. Therefore, the given prerequisites are applied to Jira native FixVersion field.
   
   
   1. PIs must have the same start and end dates for each team / project in the ART. In SAFe this is usually the first and last days of the quarter, and PIs are often called something like Q1, 2019 Q1, Q1 '19 or similar
      Note that this doesn't require sprints to start and end at the same time, because in practice some teams may be a day or two off from other teams. 
   2. PI must have the same name across all teams / projects in the ART.
   3. Tickets where you indicate the business value (BV) are all assigned to a PI.
   4. PIs for the past periods are marked as complete because the report only accounts for the completed PIs. That is you mark the respective version in the Releases section of each project as released.
      
      
3. Issue type for tracking the business value is configured
   1. Use the necessary issue type for tracking the business value or create a new one for this.
      Now the gadget supports the following issue types:
      • Feature – this is a Jira's Epic issue type renamed to Feature using the SAFe EPIC to Feature Translator for Jira.
      • Capability – new issue type that you can create in Jira. 

      • Portfolio Epic – new issue type that you can create in Jira. 

   2. Make sure that all projects inside a particular PI use the same issue type for tracking business value because you select one issue type for the report.
      
      
4. Business Value field exists and is properly set up
   1. Number Jira custom field.
   2. It must have one of the following names "BV" or "Business Value".
   3. This field is configured for the projects that you want to report on or is global (recommended).
   4. This custom field is configured to appear in one of the issue types that the gadget supports - Feature (renamed Epic issue type), Capability, or Portfolio Epic.
   5. You have business value entered for all tickets that you want to track for the report.
      

   6. BV containing tickets must be marked as done to get into the report because it takes into account only completed work. 
      It might happen that a BV containing ticket (Feature for instance) is completed but it has children tickets that are not yet completed. In this case the report will count this feature in but will display a warning so that you take a look at those. Maybe children tickets will need to be tied to another Feature or maybe they will need to be closed, or a Feature - reopened. 

Fields description

Tips for the Program Predictability Measure report

For you to have a meaningful data on the report, check on the following items:

...

1. Agile Release Train custom field is a global Jira custom field, that must be created and configured in Jira, not by a 3rd party plugin and it has this exact name.
2. It will be a single select, so one ticket should only be able to have one value for the ART field.
3. All projects / teams in the report should belong to one ART because a report shows data for one ART at a time.

...

1. PI = Jira's FixVersion field
2. PIs start and end on the same day for each team. Sprints should also ideally begin/end at the same time for all teams, but in practice some teams may be a day or two off from other teams. This does not impact the way the gadget calculates data. 
3. PI (FixVersion) must have the same name for every project in the chart.

...

1. A proper issue type for these tickets should be created. This can be one of the following:
   1. Feature
   2. Capability
   3. Portfolio Epic
   4. "Epic" issue type that is renamed to "Feature" using the E2F plugin
2. BV containing tickets must be marked as done to get into the report.

...

See also

PPM - Using Program Predictability Measure report