Importing issues and sprints from Jira to Agile Development 2.0

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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 issues and sprints from Jira to Agile Development 2.0

    This guide explains how ServiceNow customers can import existing issues and sprints from Jira into Agile Development 2.0 (version Yokohama and later). It enables synchronization between Jira and Agile Development 2.0, allowing updates on epics, stories, and sprints to reflect automatically in both systems. The import process supports importing Jira project issues as stories and epics, and Jira board sprints into Agile Development 2.0 sprints.

    Show full answer Show less

    Key Features

    • Importing Issues: From version 2.0.1, issues can be imported directly after discovering Jira projects without requiring team integration settings. Imported issues initially lack assignment groups but can be manually assigned. Creating team integration settings links Jira projects to Agile 2.0 assignment groups, enabling automatic assignment of imported issues.
    • Importing Sprints: Sprint data import requires Jira boards to have team integration settings associating them with Agile 2.0 assignment groups. Only sprints that have started, and are either current or completed in Jira, are imported into the corresponding Agile 2.0 assignment group.
    • Team Integration Settings: Replacing the earlier Project Integration Settings module from version 2.0.1, team integration settings associate Jira projects and boards with Agile 2.0 assignment groups. This association enables bidirectional synchronization of issues, epics, and sprints, allowing visibility and updates across both platforms.

    Practical Use for ServiceNow Customers

    • Associating Jira Projects and Boards: By linking Jira projects and boards with Agile Development 2.0 assignment groups, customers enable seamless import and export of issues, epics, and sprints.
    • Issue Management: Import issues to Agile Development 2.0 to update and manage them directly, with the option to assign issues automatically through team integration.
    • Sprint Tracking: Import current and completed Jira sprints to track sprint progress within Agile Development 2.0, ensuring alignment between Agile planning and execution tools.

    Implementing these import processes facilitates integrated agile project management by maintaining synchronized records between Jira and Agile Development 2.0, enhancing visibility and collaboration across teams.

    Understand the process of importing existing issues and sprints from Jira to Agile Development 2.0.

    You can import existing issues from Jira projects as stories and epics, and existing sprint data from Jira boards as sprints to Agile Development 2.0. After importing the available data, any updates that you make to the epic, story, or sprint records will be synchronized automatically in both Jira and Agile Development 2.0.

    Importing issues

    From version 2.0.1, you can proceed to import issues from a Jira project directly after discovering projects from Jira. You do not have to create team integration settings. However, the imported issues are not associated to any assignment group in Agile Development 2.0. You can manually assign these issues to an assignment group later.

    If you want your imported issues to be assigned to an assignment group automatically, you can create team integration settings for your Jira project by associating it to an Agile 2.0 assignment group and then proceed to import the issues. This setting ensures that any imported issues that belong to a Jira project are assigned to its associated assignment group.

    Importing sprints

    Importing sprint data from Jira boards require that the board has team integration settings that associate it to an Agile 2.0 assignment group. Sprint data of a Jira board is imported to its assignment group, only if these sprints have already started in Jira. Also, only the completed and current sprints of Jira are imported.

    Team integration settings

    From version 2.0.1, the Project Integration Settings module is available as Team Integration Settings. Team integration settings help you associate Jira projects and boards with Agile 2.0 assignment groups to facilitate the bidirectional synchronization of record updates.

    Associating a Jira project to an assignment group allows the following:
    • Enable import and export of all available stories and epics between this project and its associated group.
    • View any new stories and epics or updates made to the existing stories and epics in both Agile Development 2.0 and Jira.
    Associating a Jira board to an assignment group allows the following:
    • Import all completed and current sprints from this board into the associated group.
    • View any completed and current sprints or updates made to them in both Agile Development 2.0 and Jira.

    To understand the workflow of the import and export of issues between Agile Development 2.0 and Jira, see Importing and exporting issues between Agile Development 2.0 and Jira.