# Feature JIM-297 - Move migrator's connection checks to health reports

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.1.0 |
| Sprint | Sprint 18.11.-24.11.2026 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | Alfonso Mancilla |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an administrator migrating from Jira  
**I want to** see the result of the connection check as one report, shown the same way across pages  
**so that** I can tell what&#x27;s wrong with a configuration and fix it before I start an import.

**Acceptance criteria**

*   &nbsp;The connection check shows as a health report
    
    *   The configuration form, in a side panel next to the form.
        
    *    The first section of the import run, where it fetches data.
        
*   The report covers all the existing checks.
    
*   Each failed check says what is wrong and how to fix it.
    
*   &quot;Test connection&quot; moves into the form&#x27;s side panel.
    
*   Fetching data in an import run runs the same checks first, and stops if one fails.
    

**Technical notes**

*   Build on core health reports (&#x60;HealthReports::Validator&#x60;).
    
*   One validator for the Jira connection, used by Test connection and by the fetch data job.
    
*   Use existing components, similar to how file storages, wiki providers and LLM connections do.
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
*   _When is it not visible?_
    

**Translation considerations**

*   _Key terms and phrases in the key languages_ 
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
