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, allowing seamless synchronization and progress tracking across both platforms. It covers importing Jira issues as stories and epics, importing sprint data from Jira boards, and configuring team integration settings to automate assignment and synchronization.

    Show full answer Show less

    Importing Issues

    • From Agile Development 2.0 version 2.0.1, you can import Jira project issues directly without first creating team integration settings.
    • Imported issues initially have no assignment group in Agile Development 2.0; manual assignment is required unless team integration is configured.
    • Creating team integration settings associates a Jira project with an Agile 2.0 assignment group, enabling automatic assignment of imported issues to that group.
    • After import, any updates to epics or stories synchronize automatically between Jira and Agile Development 2.0.

    Importing Sprints

    • Importing sprint data requires that the Jira board is linked to an Agile Development 2.0 assignment group through team integration settings.
    • Only sprints that have started in Jira and are either current or completed can be imported into Agile Development 2.0.
    • Imported sprints are associated with the corresponding assignment group for tracking and synchronization.

    Team Integration Settings

    • Available from version 2.0.1, team integration settings replace the previous Project Integration Settings module.
    • These settings link Jira projects and boards with Agile Development 2.0 assignment groups to enable bidirectional synchronization of issues and sprints.
    • Associating a Jira project enables import/export and update visibility for all stories and epics between Jira and Agile Development 2.0.
    • Associating a Jira board enables import/export and update visibility for current and completed sprints.

    Practical Benefits for ServiceNow Customers

    • Easily import and synchronize Jira issues and sprints into Agile Development 2.0 to maintain a unified view of Agile work.
    • Automate assignment of imported issues by configuring team integration, reducing manual management effort.
    • Track sprint progress directly in Agile Development 2.0 with synchronized data from Jira boards.
    • Ensure updates in either Jira or Agile Development 2.0 reflect automatically in the other system, supporting collaboration across teams using both platforms.

    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. To do so, associate it with an Agile 2.0 assignment group, and then 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.