--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-business-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Importing and exporting issues between Agile Development 2.0 and Jira # Importing and exporting issues between Agile Development 2.0 and Jira {#ariaid-title1} Release version: Australia Updated October 21, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Importing and Exporting Issues between Agile Development 2.0 and Jira This guide explains how to import and export issues between ServiceNow Agile Development 2.0 and Jira by configuring team integration settings for Jira projects. It details how epics, stories, attachments, comments, and sprints synchronize between the two platforms, maintaining relationships and key field mappings. Show full answer Show less ## Importing to Agile Development 2.0 from Jira * Creating an epic or story in Jira automatically creates the corresponding epic or story in Agile Development 2.0, assigned according to team integration settings. * The relationship between stories and their epics is preserved as in Jira. * The **Assigned To** field in Agile Development 2.0 shows the Jira user only if a matching email exists in ServiceNow. * Only fields defined in the configured field map import to Agile Development 2.0. * Attachments added in Jira are also added to the matching Agile Development 2.0 story or epic. * Comments from Jira appear as work notes in Agile Development 2.0; images in comments become attachments. * Deleting an issue in Jira deletes the corresponding Agile Development 2.0 record if deletion is enabled in table settings. * Starting a sprint in Jira creates a corresponding sprint in Agile Development 2.0 when configured. ## Exporting from Agile Development 2.0 to Jira * Creating epics or stories in Agile Development 2.0 exports them to Jira projects as configured, maintaining epic-story relationships. * Updates to the **Assigned To** field in ServiceNow sync back to Jira. * Attachments and work notes from Agile Development 2.0 export to Jira as corresponding attachments and comments. * State changes in Agile Development 2.0 export as workflow transitions to Jira, but only if the Jira workflow supports the mapped transition name. * Changing the assignment group of a story in Agile Development 2.0 recreates the Jira issue in the newly associated Jira project. * Sprints created in Agile Development 2.0 export to Jira if the Jira board is set in team integration. * Exports may fail if Jira enforces transition rules that conflict with Agile Development 2.0's state changes (e.g., skipping required intermediate statuses). ## Practical Considerations for ServiceNow Customers * Ensure proper configuration of team integration settings to enable seamless sync of issues, assignments, attachments, comments, and sprints between Agile Development 2.0 and Jira. * Verify user email consistency between Jira and ServiceNow to correctly map the Assigned To field. * Customize field mappings and workflow state configurations to align with your Jira workflows and avoid sync errors. * Enable deletion permissions in ServiceNow tables if you want issue deletions to propagate from Jira. * Be aware of Jira workflow transition rules to prevent export failures due to invalid state changes. Understand the workflow for the import and export of issues between Agile Development 2.0 and Jira. To export and import issues between Agile Development 2.0 and Jira, you must complete the [team integration settings](https://www.servicenow.com/docs/hgfOaWFk1zYlIjE39qqz3w "Associate your Jira projects and boards with assignment groups in Agile Development 2.0 to enable import and export of all available issues between the associated project and assignment group.") for your Jira projects. ## Importing to Agile Development 2.0 from Jira {#import-export-issues-sn-jira-workflow__section_lhg_b4s_hkb} * When you create an issue of type epic in a Jira project, an epic is created for the assignment group according to the team integration settings you configured. * When you create an issue of type story in a Jira project, a story is created for the assignment group according to the team integration settings that you configured. * The relationship between the story and its epic is retained as it is in Jira. * The Assigned To field in the story displays the user from Jira, only if a user with the same email address is found in Agile Development 2.0. {#import-export-issues-sn-jira-workflow__ul_wnz_n4s_hkb} * Only the fields that are defined in the field map are retained in the story or epic. For details of the default mapping configuration, see [Default mapping configuration between Agile Development 2.0 and Jira](https://www.servicenow.com/docs/DEtUFK5tRRIfZTnlFQlBhg "Understand the default field mapping configuration for work items of a project between Jira and Agile Development 2.0."). * When you add an attachment to an issue in Jira, the same attachment is added to the corresponding story or epic in Agile Development 2.0. * When you add comments for an issue in Jira, they are updated in the Work notes field of the story or epic in Agile Development 2.0, based on the map configuration. Note: The images added in the comments appear as attachments. * When you delete an issue in Jira, the corresponding record is deleted in Agile Development 2.0. Note: To delete records in Agile Development 2.0, set the Can Delete field to true in the Application access of the respective tables. For details, see [Table design and runtime settings](https://www.servicenow.com/docs/access?context=r_TableApplicationAccessFields&version=australia&pubname=australia-application-development&ft:locale=en-US). * When you start a sprint in Jira, a sprint is created for the assignment group in Agile Development 2.0, if the Jira board is configured in the team integration settings. {#import-export-issues-sn-jira-workflow__ul_skc_n4s_hkb} |-|-| | Figure 1. Import workflow for issue created in Jira | Figure 2. Import workflow for issue updated in Jira | [ ] {#import-export-issues-sn-jira-workflow__table_qcf_mxs_hkb} ## Exporting from Agile Development to Jira {#import-export-issues-sn-jira-workflow__section_mvh_fqs_hkb} * When you create an epic for an assignment group, it is exported to the project in Jira according to the team integration settings that you configured. * When you create a story for an assignment group, it is exported to the project in Jira according to the team integration settings that you configured. * The relationship between the story and its epic is retained in Jira. * Updates to the Assigned To field in the ServiceNow platform is exported to Jira. {#import-export-issues-sn-jira-workflow__ul_b2w_5qs_hkb} * When you add an attachment to a story or an epic, the same attachment is added to the corresponding issue in Jira. * When you add work notes to a story or an epic, they are updated in the corresponding issue in Jira as comments. * When you change the State of a story, the change is exported to Jira as a workflow transition. Note: The export succeeds only if the Jira workflow allows a transition with the mapped name from the current status of the issue. For example, if the workflow has no transition from To Do to Done, moving a story directly to Done leaves the Jira status unchanged. The mapped name is the External Choice Name value in the choice map. For more information, see [Customize your workflow state configuration](https://www.servicenow.com/docs/JI240kTb8IUqccOPvAC3EA "Create a custom workflow state map of your preference for a Jira project."). * When you update the assignment group of an existing story in Agile Development 2.0, the issue is recreated in the Jira project that is associated with the updated assignment group. * When you create a sprint for an assignment group in Agile Development 2.0, it is exported to Jira only if you configured the Jira board in the team integration settings. Note: If your Jira instance has state transition rules, the export sync from Agile Development 2.0 to Jira might fail. For example, if a transition rule in Jira restricts a story or work item from moving directly to a Complete state without first passing through an In Progress state, and the story is marked Complete without that intermediate step, the sync fails. {#import-export-issues-sn-jira-workflow__ul_qdw_gqs_hkb}