Importing and exporting issues between Agile Development 2.0 and Jira

  • Release version: Zurich
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    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, focusing on the synchronization of epics, stories, attachments, comments, and sprints. Proper configuration of team integration settings is essential to enable seamless data exchange between the two platforms.

    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 based on team integration settings.
    • The hierarchical relationship between stories and epics in Jira is maintained during import.
    • The Assigned To field is populated only if a matching user with the same email exists in Agile Development 2.0.
    • Only fields defined in the configured field map are retained on imported issues.
    • Attachments added in Jira issues are mirrored in Agile Development 2.0.
    • Comments from Jira issues are imported into the Work notes field in Agile Development 2.0; images in comments appear as attachments.
    • Deleting an issue in Jira deletes the corresponding Agile Development 2.0 record if the Can Delete permission is enabled on relevant tables.
    • Starting a sprint in Jira creates the sprint in Agile Development 2.0 for the configured assignment group.

    Exporting from Agile Development 2.0 to Jira

    • Creating epics or stories in Agile Development 2.0 exports them to the associated Jira project based on team integration settings.
    • The relationship between stories and epics is preserved in Jira.
    • Updates to the Assigned To field in Agile Development 2.0 are reflected in Jira.
    • Attachments and work notes (exported as comments) on Agile Development 2.0 issues are synchronized to Jira.
    • Changing the assignment group for a story in Agile Development 2.0 recreates the issue in the corresponding Jira project.
    • Creating sprints in Agile Development 2.0 exports them to Jira only if the Jira board is configured in team integration settings.
    • Note that Jira state transition rules may cause export synchronization failures, for example, if a story is marked Complete in Agile Development 2.0 without following required transition states in Jira.

    Practical Considerations for ServiceNow Customers

    To enable smooth integration and synchronization:

    • Ensure team integration settings between Agile Development 2.0 and Jira are correctly configured.
    • Configure field mappings to control which issue fields are synchronized.
    • Verify user email addresses exist in both systems to enable proper assignment syncing.
    • Enable delete permissions in Agile Development 2.0 tables if you want deletions in Jira to propagate.
    • Be aware of Jira workflow state transition rules that may impact export success.

    Following these guidelines helps maintain consistency and traceability of development work items across ServiceNow Agile Development 2.0 and Jira.

    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 for your Jira projects.

    Importing to Agile Development 2.0 from Jira

    • When you create an issue of type epic in a Jira project, an epic is created for the assignment group according to your configured team integration settings.
    • 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.
    • 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.
    • 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.
    • 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.
    Figure 1. Import workflow for issue created in Jira
    Import for issue created in Jira
    Figure 2. Import workflow for issue updated in Jira
    Import for issue updated in Jira

    Exporting from Agile Development to Jira

    • 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.
    • 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 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.