Jira Align: Bulk move unintegrated stories to Jira

Summary

Learn how to move stories from Jira Align to Jira for programs not currently integrated through the Jira connector. This applies to Atlassian Cloud.

Overview

You may need to move stories from Jira Align to Jira when decommissioning programs or migrating data from non-integrated programs into a Jira project for tracking and execution..

Solution

Choose one of the following three methods based on your technical resources and whether you want to use the existing Jira connector.

Option 1: Use the Jira connector (Recommended for bulk sync)

Even if your programs are not currently integrated, you can temporarily map them to trigger a data push to Jira. This method ensures that the connector handles the creation of issues.

• Map the Program: In Jira Align, navigate to Jira Settings, then Manage Projects and create a mapping between the Jira Align Program and the destination Jira Project.

• Enable Bidirectional Sync: Ensure that the setting Allow story sync from Jira Align to Jira is set to Yes under Jira Settings, then Jira Setup.

• Trigger the Sync:

  • Once the mapping is active, any update to a story in Jira Align will trigger the connector to create the issue in Jira.

  • Use the Multi-Select tool on the Story Grid to perform a bulk update (such as adding a temporary tag or changing a field value) on all stories you wish to move. This "touch" signals the connector to sync them to the mapped Jira project.

Option 2: Excel export and import

If you are permanently moving programs out of Jira Align and do not wish to configure new connector mappings, a manual export and import is the most straightforward way to capture historical data.

• Navigate to the Story Grid in Jira Align.

• Export the stories to an Excel file.

• In Jira, use the External System Import to upload the CSV file and map the fields to your Jira project.

Option 3: Jira Align API (For technical teams)

If you have development resources, you can use the Jira Align API to programmatically retrieve story data and post it to the Jira API. This allows for a highly customized migration but requires significant technical effort to handle authentication, data mapping, and error handling for both platforms.