# Epic JIM-249 - Add configuration options especially regarding mapping and users 

Project: Stream Jira to OpenProject data Migrator
Status: in specification
URL: https://community.openproject.org/work_packages/JIM-249

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q1 |
| Date |  |
| Votes |  |
| List | RM Jira Migrator |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Wieland Lindenthal |
| Product manager | Kristine Jetzke |
| Feature Lead |  |
| Designer | Marc Alcobé |
| Developers | OP Dev Pro Team |
| Requested by |  |
| Interest by | Home (224196000003952096) |

## Estimates and progress

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

## Description

**As** an OpenProject admin performing migrations from Jira&nbsp;  
**I want to** be able to configure the import  
**so that** I have the desired data in OpenProject

**Acceptance criteria**

*   In the Jira configuration the following options can be set and are considered by the migrator
    
    *   Users &amp; Groups
        
        *   Skip user creation: All encountered users are expected to already exist in OpenProject. If they do not exist, the import fails.
            
        *   Skip group creation: No user groups are created.
            
    *   Field Mapping
        
        *   Mapping Table for Status field (e.g. map Jira status Open to OpenProject status New, map Jira status Done to OpenProject status closed)
            
        *   Mapping Table for Resolution values
            
        *   Mapping Table for Priority field (e.g. map Jira status Minor to OpenProject status Low)
            
        *   Mapping Table for Type field (e.g. map Jira type Sub-Task to OpenProject type Task)
            
        *   Mapping Table for Custom fields
            
        *   Mapping relationship names
            
    *   Field Exclusion
        
        *   Skip import of Resolution fields (Resolution and Resolution Date)
            

**Technical notes**

*   The configuration should be persistent for a run i.e. if it is changed in the Jira configuration while an import is running, the configuration that was active when the run was started should be used for the whole run
    

**Out of scope**

*   Configuration of individual runs. This feature will very likely need to be added later on e.g. in order to allow status mappings per project
    
*   Global configuration for all Jira instances
    

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