# Feature JIM-309 - Migrate custom fields of type Version Picker (single and multiple)

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.1.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List | RM Jira Migrator |
| Roadmap | 2027 Q1 |
| 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 |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a Jira admin migrating to OpenProject  
**I want to** migrate custom fields of type &quot;Version Picker&quot; to the &quot;version&quot; custom field in OpenProject  
**so that** my users can work as before.

**Acceptance criteria**

*   Custom fields of type &quot;Version Picker (single version)&quot; are migrated to OpenProject custom field User with the same name. The value &quot;Allow multi-select&quot; is set to false.
    
*   Custom fields of type &quot;Version Picker (multiple versions)&quot; are migrated to OpenProject custom field User with the same name. The value &quot;Allow multi-select&quot; is set to true.
    
*   Versions that exist as values in one of the fields should be created as versions in OpenProject if they don&#x27;t exist yet. If the version no longer exists in Jira, a warning should be logged.
    

**Technical notes**

*   I assume that &quot;Allow non-open versions&quot; might need to be set to true during the migration or be ignored.
    

**Permissions and visibility considerations**

*   _\-_
    

**Translation considerations**

*   _\-_
    

**Out of scope**

*   \-
    

<br>
