# Feature JIM-109 - Migrate Jira Labels

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Target versions | 18.0.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List | RM Jira Migrator |
| Roadmap | 2026 Q4 |
| Relevance | Very Important — Required Immediately After Go-Live |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Integrations / Jira |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Community (COM) |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Wieland Lindenthal |
| Product manager | Kristine Jetzke |
| Developers | Andrej Sandorf |
| Designer | Marc Alcobé |
| Ordered by |  |
| Signed off by |  |
| Interest by | Home (224196000003952096) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work | 10d 0h |
| Labor costs |  |

## Description

**As** an administrator migrating projects from Jira to OpenProject  
**I want to** have the labels set on Jira issues imported as OpenProject labels on the resulting work packages  
**so that** the categorisation our teams built up in Jira survives the migration and stays usable for filtering and grouping in OpenProject.

**Acceptance criteria**

*   Every value in a Jira issue's `labels` field becomes a label on the imported work package.
    
*   Label names are matched against existing OpenProject labels case-insensitively. An existing label is reused; a new one is created only when no match exists.
    
*   Two Jira labels that differ only in case (`Backend` / `backend`) collapse into the single existing OpenProject label. The label is not renamed.
    
*   Re-running an import (or importing a second project that uses the same label) reuses the label created by the earlier run instead of creating a numbered duplicate.
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
    *   To everyone who can see the imported work package.
        

**Out of scope**

*   Jira custom fields of type `com.atlassian.jira.plugin.system.customfieldtypes:labels`. These are already imported as list custom fields and keep that behaviour.
    
*   Label colours, descriptions, grouping or project-scoped labels. Labels on anything other than issues.
    
*   Mapping or renaming rules for label names during the import, for example merging synonyms or stripping prefixes.