Importing issues and sprints from Jira to Agile Development 2.0
Summarize
Summary of Importing Issues and Sprints from Jira to Agile Development 2.0
This guide explains how to import existing issues and sprints from Jira to Agile Development 2.0, enabling synchronization between the two platforms. Users can import issues as stories and epics, and sprints from Jira boards, facilitating project management within Agile Development 2.0.
Show less
Key Features
- Importing Issues: Starting with version 2.0.1, users can import issues directly from Jira after discovering projects without needing to set up team integration settings. Imported issues initially lack assignment group associations but can be manually assigned later.
- Automatic Assignment: To automatically assign imported issues to a designated assignment group, users must configure team integration settings linking the Jira project to the Agile 2.0 assignment group.
- Importing Sprints: Sprint data can only be imported from Jira boards that have team integration settings. Only current and completed sprints will be imported, ensuring updates reflect accurately in both systems.
- Team Integration Settings: This module facilitates bi-directional synchronization, allowing users to import and export stories, epics, and sprints between Jira and Agile Development 2.0.
Key Outcomes
By associating Jira projects and boards with Agile Development 2.0 assignment groups, users can streamline their workflow, allowing for real-time updates and tracking of issues and sprints. This integration ensures that project management remains coherent and up-to-date across both platforms, improving efficiency and collaboration.
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.
- 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.
- 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.