Importing and exporting issues between Agile Development 2.0 and Jira

  • Release version: Yokohama
  • 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 the workflow for importing and exporting issues between Agile Development 2.0 and Jira, enabling seamless integration and synchronization of project data. To enable these operations, team integration settings must be configured for your Jira projects.

    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 for the configured assignment group.
    • The relationship between stories and epics is preserved as it exists in Jira.
    • The Assigned To field in Agile Development 2.0 populates only if a matching user email exists in both systems.
    • Only fields defined in the field mapping are retained during import.
    • Attachments and comments added in Jira are imported into Agile Development 2.0; comments appear as work notes and images in comments are added as attachments.
    • Deleting an issue in Jira deletes the corresponding record in Agile Development 2.0, provided the Can Delete field is enabled in the application access settings.
    • Starting a sprint in Jira creates a corresponding sprint in Agile Development 2.0 if the Jira board is integrated in the team settings.

    Exporting from Agile Development 2.0 to Jira

    • Creating epics and stories in Agile Development 2.0 exports them to the associated Jira project based on team integration settings.
    • Story-epic relationships are maintained in Jira.
    • Updates to the Assigned To field in Agile Development 2.0 sync to Jira.
    • Attachments and work notes in Agile Development 2.0 transfer to Jira as attachments and comments respectively.
    • Changing an assignment group on a story in Agile Development 2.0 results in the issue being recreated in the corresponding Jira project.
    • Sprints created in Agile Development 2.0 export to Jira only if the Jira board is configured in integration settings.
    • Be aware that Jira state transition rules may cause export synchronization failures if the Agile Development 2.0 status updates do not comply with Jira’s workflow constraints.

    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 the team integration settings that 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.
    • 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.