# Feature OP-18550 - Primerize Custom Field forms

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-18550

## Planning

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

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| OP-18979 | Bug | WP CF of type List does not display info banner upon creation | closed |  | 17.2.0 |  | Administration / Custom fields, Frontend components and Primer design system, Administration |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Administration / Custom fields, Administration / Custom actions, Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | Henriette Darge, Alexander Coles |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a administrator of OpenProject  
**I want to** be able to manage custom fields with ease  
**so that** my instance of OpenProject works for its users

**Acceptance criteria**

*   Primerize the Admin/Custom Field forms which were not primerized yet
    
*   For Fields of type &quot;List&quot;, there will be a separate tab &quot;items&quot; (like for hierarchy and weigthed item lists)
    
    *   The tab shows the current options table as it is
        

**Technical notes**

*   &nbsp;We plan to migrate the list fields into the hierarchy fields and can then use the existing components on the items tab. Therefore it makes no sense to invest time into primerizing the current options table.
    

**Permissions and visibility considerations**

*   Admin-only
