Content
View differences
Updated by Pavel Balashou 2 days ago
### Steps to reproduce
1. Import a project from Jira using Jira Migrator.
2. Stop on Review mode step.
### What is the buggy behavior?
* The page lacks information about migrated data.
* The only created objects are represented in the list.
* created projects
* created work\_packages
* created users
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/920625/content">
### What is the expected behavior?
1. Both created and existing entities that are used during import are listed here.
1. Types
2. Priorities
3. Roles
4. Statuses
5. Users
6. Groups
2. All users that are involved in migrated projects are shown here properly.
3. All entities have useful links.
4. Jira users migrated with blank email should be highlighted.
## Why?
Basically, it is needed to impove transparency what is happening during an import run.
1. Import a project from Jira using Jira Migrator.
2. Stop on Review mode step.
### What is the buggy behavior?
* The page lacks information about migrated data.
* The only created objects are represented in the list.
* created projects
* created work\_packages
* created users
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/920625/content">
### What is the expected behavior?
1. Both created and existing entities that are used during import are listed here.
1. Types
2. Priorities
3. Roles
4. Statuses
5. Users
6. Groups
2. All users that are involved in migrated projects are shown here properly.
3. All entities have useful links.
4. Jira users migrated with blank email should be highlighted.
## Why?
Basically, it is needed to impove transparency what is happening during an import run.