Can the Team associated with an Iteration be updated?

[Kelley_Cooper]

Is it possible to update the Team associated with an Iteration?  In all locations I see the value in the Team field is a link, not an editable field.  I'm able to update the Program associated with the Team Iteration, but not the Team (this is needed as the original Team has moved to a new Program and a different Team name was added by the Jira Align Connector).

Thank you for any help!

K

Kelley Cooper

[Peter Jessen]

Hi @Kelley_Cooper

Hi Kelley,

Short answer is no, you can't update the team associated with an iteration/sprint, from the sprint list screen. You can change the team name from the team detail page. The question is what are you trying to achieve by doing this? Each sprint in Jira Align is uniquely tied to a team based on the board/sprint association in Jira.

If a team has been moved from one program to another, then there are some critical settings in the connector that need to be configured properly. Without understanding exactly how your organization is configured, I can't provide you the proper config because it has to do with if you use one Jira project for a program or one project per team and one project for features (Jira epics). Depending on your config, you could change the team name back to the original team name, subject to a bunch of caveats around whether or not you care about the team metrics staying under the original program or you're fine with them migrating to the new program. Also, was the original board re-pointed to the new program and the original sprints are still being used in Jira? Or are new sprints being used? It sounds like you might be using the original sprints.

So why can't you change the team name on a sprint? The reason for this has to do with how Jira Align takes the (mostly) non-normalized data from Jira (which lacks a team object and sprint object in the data structure) and converts that data via the connector to create a team and related sprints in Jira Align. Jira Align requires each board to have its own set of unique sprints, so each sprint it uniquely linked to one and only one team. When your org moved the team to the new program, the new team name was added probably because a new board was added to represent the team on the new program in Jira Align.

Solving this is actually much easier than it sounds, if all the parameters are known and the intended outcome.

Regards,
Peter