# Epic JIM-62 - Jira Migrator shows progress during import of projects, leveraging concurrency

Project: Stream Jira to OpenProject data Migrator
Status: closed
URL: https://community.openproject.org/work_packages/JIM-62

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups | https://www.figma.com/design/959fRLTsmhOiHkXYPfd0D2/Jira-import-admin-settings?node-id=270-8295&t=KDAPXxM3RqfCWHBM-0 |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2026 Q3 |
| Date |  |
| Votes |  |
| List | RM Jira Migrator |
| Target versions | 17.9.0 |
| Sprint | Sprint 3 |
| Backlog bucket |  |
| Relevance |  |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| JIM-200 | Implementation | Performance regression: Custom fields import runs per import job | closed | Pavel Balashou | 17.9.0 | Stream Jira to OpenProject data Migrator | Medium |  |
| JIM-204 | Implementation | Make sure jira import stages run in order | closed |  | 17.9.0 | Stream Jira to OpenProject data Migrator | Medium |  |
| JIM-208 | Implementation | Add progress bar slot for BorderBoxListComponent | new |  |  | Stream Jira to OpenProject data Migrator | Medium |  |
| JIM-209 | Implementation | Use updated BorderBoxListComponent in jira import wizard | new |  |  | Stream Jira to OpenProject data Migrator | Medium |  |
| JIM-214 | Implementation | Refactor jira_staged_import_job.rb | new |  |  | Stream Jira to OpenProject data Migrator | Medium |  |
| JIM-218 | Implementation | Open review issues | closed |  |  | Stream Jira to OpenProject data Migrator | Medium |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Module |
| --- | --- | --- | --- | --- | --- | --- |
| JIM-201 | Bug | Scale progress wizard better for a big number of projects | closed |  | 17.9.0 |  |
| JIM-217 | Bug | Cannot collapse Jira import sections | rejected | Pavel Balashou | 17.9.0 | Integrations / Jira |
| JIM-212 | Bug | Alignment issues on Jira import tables | confirmed |  | 18.0.0 |  |
| JIM-210 | Bug | Jira import errors are not legible in dark mode | confirmed |  | 18.0.0 | Integrations / Jira |
| JIM-215 | Bug | Jira migrator progress bars overflow on smaller screens | rejected |  |  | Integrations / Jira |
| JIM-216 | Bug | Cannot abort a Jira import | confirmed | Pavel Balashou |  | Integrations / Jira |

## Details

| Attribute | Value |
| --- | --- |
| Module | Integrations / Jira |
| Enterprise plan | Community (COM) |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Pavel Balashou |
| Product manager | Kristine Jetzke |
| Designer | Marc Alcobé |
| Developers |  |
| Requested by |  |
| Interest by | Home (224196000003952096) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

**As** an administrator migrating data from Jira to OpenProject  
I **want to** see real time progress how project imports are progressing  
**so that** I have an indication that the import is healthy and not stuck.

I also want to know that the Migration tool is doing its best to speed up the import by leveraging concurrency. If I have to wait for a long time, I want to know that OpenProject already tries its best to be fast.

<https://www.figma.com/design/959fRLTsmhOiHkXYPfd0D2/Jira-import-admin-settings?node-id=926-5741&amp;t=jfhCkfPSsEwGvo75-0>

**Acceptance criteria:**

  - The UI updates on progress

  - The UI shows concurrent jobs

  - In "import data" stage you have "Abort" button. 
    
      - Except the Approval/Revert step. This stage is not abortable. Instead you have an option to approve or revert. Both of them can't be aborted.
    
      - Abort changes Import run state to "Aborted".
    
      - In "Aborted" state there are "Revert" and "Continue/Resume" buttons.
    
      - Abort stops jobs mid run.
    
      - Note: the aborting of the previous data fetching stages is handled in <mention class="mention" data-id="77770" data-type="work_package" data-text="#JIM-145" data-display-id="JIM-145">\#JIM-145</mention>