Importing and exporting issues between Agile Development 2.0 and Jira

  • Release version: Washingtondc
  • Updated September 6, 2024
  • 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 document outlines the process for importing and exporting issues between Agile Development 2.0 and Jira. Proper team integration settings for your Jira projects are essential for successful data transfer.

    Show full answer Show less

    Key Features

    • Importing from Jira: When an epic or story is created in Jira, corresponding items are automatically created in Agile Development 2.0, maintaining their relationships.
    • Field Mapping: Only fields defined in the mapping configuration are retained during import.
    • Attachments and Comments: Attachments and comments from Jira are carried over to Agile Development 2.0, with images appearing as attachments.
    • Deletion Synchronization: Deleting an issue in Jira will remove the corresponding record in Agile Development 2.0, given that the Can Delete field is set appropriately.
    • Sprint Management: Starting a sprint in Jira creates a corresponding sprint in Agile Development 2.0, contingent on team integration settings.
    • Exporting to Jira: Epics and stories created in Agile Development 2.0 are exported to Jira while maintaining their relationships.
    • Attachment and Work Notes Sync: Attachments and work notes in Agile Development 2.0 translate to Jira as attachments and comments, respectively.
    • Assignment Group Updates: Changes to the assignment group in Agile Development 2.0 lead to the recreation of the issue in the respective Jira project.
    • Sprint Export: A sprint in Agile Development 2.0 is exported to Jira only if the Jira board is configured correctly.

    Key Outcomes

    By following the outlined integration settings, ServiceNow customers can ensure seamless data synchronization between Agile Development 2.0 and Jira, enhancing visibility and collaboration across teams. Expect accurate mapping of issues, retention of important details, and streamlined management of projects across both platforms.

    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.