Team sync


The old navigation will be removed from Jira Align in early 2024.
Learn more about the upcoming changes

About this report

The team sync report lists all teams associated to the programs in the selected PI, and indicates if they participated in the PI's sprints. This report reads as a data table/matrix.

The report can be used as a tool by Scrum Masters, team leaders, and product owners to track team participation. It may be beneficial to review the report with teams during pre- and post-PI meetings, general team meetings, and during sprint review meetings. This report is generated by selecting a specific PI. 

To navigate to this report:

If you’re using the new navigation:

  1. Select Programs in the top navigation bar and select the program you want to view the report about.
  2. On the sidebar, select Reports in the list of options.
  3. Select Sprint synchronization; the report displays.

If you’re using the old navigation:

  1. Select the Reports icon from the left Nav menu.
  2. Start typing the report's name in the Search box.
  3. Once found, select the report.
    Note: You can also use the categories on the left to search for the needed reports.


  1. PI must exist in the system and be tied to a program. 
  2. Sprints must be created and tied to a PI. 
  3. Teams must be created and tied to a program.
  4. Stories must be created and tied to a sprint. 
  5. Tasks must be created and tied to stories. 

How are report values calculated? 

  • Teams listed in the report are teams that are tied to programs that are participating in the PI.
  • A checkmark in a table cell indicates that a team has generated a sprint, via the Sprint List/New Sprint panel, for the PI's sync date, which is entered on the program increments page/New Program Increment panel.
  • Statistics at the bottom of the report display the sum of all sprints generated, for all teams, for the selected PI, and the sum of all sprints, for all teams, that were not generated for the PI.


How to interpret this report

Tracking team participation may help you better estimate workloads for similar sprints and PIs in the future (e.g., capacity planning). If a sprint is not progressing as expected, look for a pattern that shows a team (or teams) that are not participating. 

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.