# Feature DREAM-902 - Update custom field labels in form configuration for types and variants 

Project: Stream Design System
Status: tested
URL: https://community.openproject.org/work_packages/DREAM-902

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0, Passion time |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| 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 | Administration / Custom fields, Administration / Type/Variants and Workflows, Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan | Community (COM) |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Henriette Darge |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**Context**

This results from the decision taken here:  
 <mention class="mention" data-id="80169" data-type="work_package" data-text="##OP-20225" data-display-id="OP-20225">\#\#OP-20225</mention>

**Acceptance criteria**

In the Form configuration page for Types and Variants, adopt this design:

<img class="image_resized op-uc-image op-uc-image_inline" style="width:616px;" src="/api/v3/attachments/924944/content">

  - Remove the "Built-in" labels that we added recently

  - ~~Display type in all fields (including built-in fields)~~

  - If a field is required, indicate it with a Label (scheme attention, "Required")

**Technical notes**

  - \[open\] For built-in fields that do not have types (eg. Start date, Finish date), we need to come up with logical types

**Permissions and visibility considerations**

  - *No change*

**Translation considerations**

  - *No change*

**Out of scope**

  - The actual index page for custom fields still need to be Primerised and will be handled separately:
    
      - Administration → Custom fields
    
      - Project settings → Work packages → Custom fields