This screenshot shows the typical results of a successful complete project import. This page is focused on providing information about the results of the data import stage.
You can see in this page a message about the successful completion of the import and two text areas with information. The first one "Import results" shows statistical results of the data import for each imported project, identified by its name:
- Time taken by data import in ms.
- Number of created users
- Number of created issues
- Number of created attachments
It would also show warnings, if any, that do not impede the import of project data but might cause the loss of some specific information (one issue, an attachment, a custom field value, etc.). Errors about the validation of the data backup or the mapping of data to the current configuration would also be shown here. If there were any of these errors, project data would not be imported.
The second one "Import trace", contains a sequence of the steps taken for importing data, and offers a much finer detail of the actions performed during the data import.
The button "Back to import complete project page" takes you back to the starting page, so that you can launch a new import of complete projects.
Under both text areas, there is a button labeled "Click here to see configuration import trace". This button opens a new page, as the one shown below, that displays the trace of the configuration import (remember that importing complete projects is done in two steps: first the configuration is imported and later the data and attachments). This is useful if you want to keep a record of all the configuration changes performed on the target instance.
Please note that starting with version 2.2.0 two configuration import traces will be displayed, as the configuration import is run in two stages (see PCP-677 for more details). The second stage imports only filters, dashboards and Agile boards and skips the rest of objects.
Users that could not be created (new since version 2.0.3)
As explained in this page (see section called "2. Setting up users and groups") when issue data is imported the plugin will create some more users, if they do not already exist. These users may be classified as "mandatory" (for example, the assignee of an imported issue) or "optional" (for example, a user that commented an imported issue). Take into account that if the import cannot create a mandatory user, import of issue data and attachments for that project will abort.
If any of these users cannot be created, the data import results page will show links to other pages that list those users, so that the JIRA admin may fix the problem. The next image shows an example of this situation, where data import for two projects aborted because mandatory users could not be created.
Clicking on the links "Some mandatory users" or "Some optional users" will open a new page, that will display the users that could not be created and the data that could be found about them. The image below shows an example of the page that displays mandatory users that could not be created. The users are grouped by imported projects: in the example shown, creating a user named "hank" would be enough for unblocking the import of project with key "SEG".
Typical situations that will cause these issues are:
- The users had been removed from the source instance
- The target instance uses external user management (for example, in a corporate LDAP server) and JIRA does not have permission to create users there.