# Feature FND-279 - Admin panel for category migration

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

## Planning

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

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| FND-294 | Implement the categories migration on the admin page | Implementation | new |  |  |  |

## 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 an** admin of an existing instance  
**I want to** decide when to turn on multiple categories  
**so that** I can update my integrations before the field changes.

**Acceptance criteria**

  - The "Categories" section on *Administration → Work packages → Versions and categories* shows the states from <mention class="mention" data-id="COMMS-839" data-type="work_package" data-text="#COMMS-839">#COMMS-839</mention>: planned changes, action required, in progress and recent changes.

  - Target versions and categories are two separate migrations. Each section has its own "Enable multiple values" button.

  - The page shows the correct content for each combination of the target versions state and the categories state.

  - "Enable multiple values" opens a danger confirmation dialog. The admin must check "I understand that this action is not reversible".

  - After confirmation, the section shows a spinner and "Enabling multiple categories". A background job turns on the setting.

  - When the job is done, the section shows "Recent changes" with the success texts and the documentation link.

  - The job repairs work packages where `category_id` and the join table disagree. It writes a catch-up journal as a system update. No false "Category changed" entry appears on the next user's save (see <mention class="mention" data-id="COMMS-985" data-type="work_package" data-text="#COMMS-985">#COMMS-985</mention>).

  - When the setting comes from an environment variable, the page shows the "not writable" hint and no button.

  - After the switch, the legacy `category` field is no longer in the API.

  - While the feature flag is off, the section shows only the planned changes.

**Technical notes**

  - Placeholder that exists today: `app/components/work_packages/admin/settings/categories_section_component.rb`.

  - Controller: `app/controllers/admin/settings/versions_and_categories_controller.rb`.

  - Figma: <https://www.figma.com/design/YjZZs8xOYcesF4JgDQWh1C/Target-versions-and-categories>

  - Analog: <mention class="mention" data-id="COMMS-839" data-type="work_package" data-text="#COMMS-839">#COMMS-839</mention>, <mention class="mention" data-id="COMMS-844" data-type="work_package" data-text="#COMMS-844">#COMMS-844</mention>.
