# Epic FND-263 - Make categories a multi-select field for work packages in order to enable migration of components

Project: Stream workspace foundations
Status: specified
URL: https://community.openproject.org/work_packages/FND-263

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

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

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2026 Q4 |
| Date |  |
| Votes |  |
| List |  |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance | Showstopper — Go-Live Blocker |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Rosanna Sibora |
| Product manager | Sonita Soth |
| Designer | Parimal Satyal |
| Developers | OP Dev Comms Team |
| Requested by |  |
| Interest by | Home (224196000003952096) |

## Estimates and progress

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

## Description

**As** a Jira admin migrating to OpenProject  
**I want to** be able to migrate issues from a project that have linked multiple components per issue  
**so that** I don't lose that information and can continue my project seamlessly in OpenProject

**Acceptance criteria**

  - On a work package I can select multiple categories.

**Technical notes**

  - Similar challenge as we did for "version --\> target versions"

**Translation considerations**

  - *Key terms and phrases in the key languages* 

**Out of scope**

  - Extending the Categories functionality <mention class="mention" data-id="72780" data-type="work_package" data-text="##FND-37" data-display-id="FND-37">\#\#FND-37</mention>