Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sprint Metrics report is not reflecting a team in the correct Program

I have a team that I moved from one program/Release train to another.  I did this in the middle of a PI.

I have updated that team to reflect the Program/release train they are now part of, but on the Sprint Metrics they still appear under the wrong Program.


I updated in Team, In Jira Settings, In Jira Management.

On the program board I see that team in the correct Program.

Not sure what Sprint Metrics is not correct

2 answers

1 accepted

0 votes
Answer accepted
Tim Keyes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 07, 2020

Hi @Ann Bouvier

It is possible that the Team's parent Program and the connector mappings were updating but the legacy sprints still need to be updated.  The following article covers how to properly migrate an Agile team from one Program to another:  I would take special note of step 4: 4. Navigate to Team > Sprints (Iterations) and update the Team’s legacy Sprint’s Program and PI fields (This step can be skipped for Kanban teams).


Updating the legacy sprints did the trick.  Thanks @Tim Keyes 

Like Tim Keyes likes this
0 votes
Tom O_Connor
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 03, 2020

I suggest opening a support case for this question.  

There are several factors that may be contributing to the move in the middle of the PI including if the Program is part of the same Portfolio or if they share the same PI among other details and understanding. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events