Move issue from one team to another in Jira does not get reflected correct in jira align.
Asked by Morten Christophersen:

I hope you can help.

I have an issue when moving issues from one team jira project to another. This only gets semi updated in jira align.

Here is the situation:

I have two team (A and B) within the same ART. They have their own jira project and sprint board.

Now I create an issue in team A:  
![issue in teamA Jira.png](https://community.atlassian.com/t5/image/serverpage/image-id/282907iD729ACCF28F06BB7/image-dimensions/339x251?v=v2 "issue in teamA Jira.png")

This gets correctly reflected in jira align:

![issue in teamA Jira align.png](https://community.atlassian.com/t5/image/serverpage/image-id/282909i2A4D8BF1BFFA8A08/image-size/large?v=v2&px=999 "issue in teamA Jira align.png")

Then (in jira) I move the issue to team B backlog:

![move.png](https://community.atlassian.com/t5/image/serverpage/image-id/282911i900FA733CEE717C6/image-size/large?v=v2&px=999 "move.png")

And result in jira is as expected (issue key is now ADZYB, instead of ADZYA):

![issue in teamB Jira.png](https://community.atlassian.com/t5/image/serverpage/image-id/282912iED9702954B1535D2/image-size/large?v=v2&px=999 "issue in teamB Jira.png")

When looking in jira Align the link to jira project is updated (green frame). However the "team" field (red frame" is not and that is my issue that this ticket is all about. As you can see the "correct" team is mentioned when pressing the drop down. But how to get this stuff to work properly?

![issue in teamB Jira align.png](https://community.atlassian.com/t5/image/serverpage/image-id/282913i34911BB496BC21B1/image-size/large?v=v2&px=999 "issue in teamB Jira align.png")

I did go through the guides I could find but they are not touching this particular issue:

<https://community.atlassian.com/t5/Jira-Align-questions/Moving-issues-between-projects/qaq-p/1952803>

<https://community.atlassian.com/t5/Jira-Align-articles/Jira-and-Jira-Align-Integration-Issue-Best-Practices/ba-p/1907851>

<https://community.atlassian.com/t5/Jira-Align-articles/Jira-and-Jira-Align-Integration-Issue-Story-and-Epic-Management/ba-p/1259396>  

I hope for some good feedback here. I have been given really good help in this forum before.


Answers:
author: Jennelle Stearns
body: [@Morten Christophersen](/t5/user/viewprofilepage/user-id/5301751) If your setup is 1 Project for the Program with each team having its owns board and sprints, I would check the team mapping field as [@Allan Maxwell](/t5/user/viewprofilepage/user-id/3502714) mentioned. However, if your setup 1 project/1 board/1 team, then I would check under Admin-Jira Settings-Jira Setup that the following is set to Yes : Allow Jira to update the team field for stories

comments: author: Morten Christophersen
body: Thanks! The latter is my case, and this seems to be doing just what I need. Thanks a lot, this was most helpful.


author: Shannon Wright
body: This could all be a timing issue related to how Align sees the Team information. Since Align assigns the team information from the Jira Management section and the Jira Boards, this could update on it's own once the timer for boards kicks off.   

If this hasn't occurred and If you haven't done this yet, try running a Jira Integration query against the issue. Go to your Admin - Jira Settings section.   
Go to the Jira Integration tab  
Select the Jira Project the issue is located  
type in the query for the issue and select the Jira Board for the new team and choose the option to run the query for that board to Yes and click Run.


author: Allan Maxwell
body: I would suggest having your Align admin validate the Team custom field id and spellings on the Team Field mapping in Jira Align:

![Screenshot 2023-09-26 at 8.53.37 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/282979iC62463706CDE442B/image-size/large?v=v2&px=999 "Screenshot 2023-09-26 at 8.53.37 AM.png")