# Feature OP-8142 - custom fields should support multi language

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-8142

## Planning

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

## 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 |  |
| 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 administrator  
**I want to** set multiple languages for a custom field name  
**so that** the user can see the correct language of the custom field name in that language set by the user

**Acceptance criteria**

*   define translations for a custom field
*   if the user set a language with none available language set the translation to english or if just one translation is available to that language.

  

**Additional acceptance criteria**

*   pre-defined custom field entries (e.g. in a type = list field) should also be translatable  
    _(raised with support ticket 13706)_
