You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
After the initial data sync is established and if the teams move issues (Features, stories) between project in Jira, will Jira Align automatically detect those changes and move them to different teams in Jira Align?
Is there an automated process to mass move?
Yes, the Move issue operation in Jira is supported by the Jira Align integration. The corresponding Jira Align work item will be reassigned to the right team in Jira Align. However, before you move the issue to the other Project, you should clear the Sprint field in the issue by moving the issue to the backlog. This will prevent a situation where the issue on the new Team's board is associated with the Sprint on another Team's board - something the Jira Align integration does not support.
To mass move issues from one Project to another, you can use Jira's built-in Bulk change function:
Thanks for the message Samit. I am looking to move in Jira Align and not Jira. So the user updated or changed the project for an issue in Jira but in JIra Align it still resides in the old project. I want to know if Jira Align can move the issues to the appropriate project
@Shyam Sundar P please clarify what you mean by "old project" in Jira Align when you say "... but in Jira Align it still resides in the old project".
The best way to make sure that Feature / Story work items in Jira Align are in sync with the Epic / Story issues in Jira when needing to move issues from one team to another, is to make those moves in Jira. The integration between Jira Align and Jira should automatically reflect that change in Jira Align - you should not have to do anything manually in Jira Align.
If the move in Jira is not getting reflected in Jira Align, then there could be an issue with the integration that may need some troubleshooting. I would suggest engaging with Atlassian support to help resolve that.
The (Feature) in Jira Align is assigned Program: A and Jira project B:
It should be assigned to Program: A and Jira Project A.
There are now security controls in place to prevent this move in Jira Align (note the Lock icon on the program selection) Once an item is assigned to a Jira project from within Jira Align, the only way to change the project is to move the item in Jira. Once the move is done in Jira, the integration will update it in Jira Align.
As @Samit Mehta _321 Gang_ mentions, if this is not updating, there is an issue within the integration. Most typically, I have seen this occur when the integration user does not have the correct permissions in the "to" project in jira. However, that is not the only reason. Open a ticket with the support team for additional assistance if needed.
Hi Tina & Samit,
My apologies was not explaining the issue correctly. I will try my best to explain the issue here.
Jira Side Project A : Board A : Issue A : Sprint A
Jira Align Project A : Team A
Jira Side Project B : Board B :
Jira Align Project B : Team B
Originally Issue1 is created in Jira in Project A and is assigned to a Sprint A in a "board A" that is part of the Project A. After sometime the issue is changed in Jira to Project B. No changes are done to the sprint for that issue. Since in Jira Align a Jira "board A" gets mapped as a team "team A" the Issue1 still sits in the same "team A" in Jira Align.
Once we went in Jira Align and manually cleared the sprint from Issue1 it went to the corresponding Project Bs team "Team B" in Jira Align.
So the question is if the Jira users makes such changes to issues is there an automated way Jira Align can understand this change.
@Shyam Sundar P my original response touched on this, but was not very clear. Before moving the issue from one Jira Project to another, make sure you first move the issue to the backlog - this will ensure that the issue is not assigned to a Sprint in the current Project. Then, when you move the issue to another Jira Project, Jira Align integration will not cause the issue you ran into with the example above.
I will update my original answer to make the above point more explicit.