...

Ensure that you are good on the following prerequisites:

...

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.

...

• The time tracking is enabled or the Story Points field is available
• Program Predictability Measure report is added to your dashboard
• You have configured the Committed vs Completed Gadget

Reading the chart

Your Program Predictability Measure Gadget displays the following information:

...