What are the implications of moving a team from 1 train to another?
I have a team that is on Train1, and I want to move them to Train2. I assume the best time to do this is at the beginning of a new PI?
What happens to any historical data for the Train and PI once that team is moved to the new train?
Hi @Ann Bouvier
As you know, you can move a team from one train to another by simply reporting the team's Jira project and Jira board from one program to another in Administrations -> Jira Settings/Jira Management. (Assuming both trains are on the same PI schedule and on the same PI objects in JA.)
The decision to be made is whether or not you want the team's historical data to stay with the original train or you don't care.
If you don't care, then simply repoint the Jira project and board. The historical data will become phantom/ghost data on the new train for all previous periods the team completed work in Jira that was synced to Jira Align.
To maintain historical data with the historical train (my preferred/recommended method) do the following.
This worked pretty well for me, but I encountered a couple of issues using the first method of not maintaining historical data:
Some story points were not showing up in various reports until the team projects and boards were synced in the Jira Settings > Jira Integration tab.
In addition, I had to change the Program related to sprints synced from Jira Cloud for any future sprints that were created before the move to the new Program. This was done via the Teams > Sprints list. (The problem was identified by the Planned vs. Accepted report having missing data.)
I made sure to change the following before syncing the projects and boards: