# Feature OP-9637 - Show custom field data by default in the UI

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| 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 |  |
| 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

### **Environment**:

Your OpenProject Version: **12.0.4** / Cloud Edition

Windows 10 / Google Chrome/ English:

### **Steps to reproduce:**

1.  Create some custom fields and include the created custom fields in all projects
2.  Create a work package using OpenProject API using the Post method (By giving custom filed information)

### **Actual Behavior**

*   The work package is created and the custom filed data is inserted into the database perfectly.
*   The issue that we facing is that the custom field data that we are posted through the API is not showing in the UI by default (all other information like subject, descriptions are shown in the UI ). 
*   It is totally unintuitive that you have to adapt the form configuration first, in order to see a new custom field.

### **Expected Behavior**

*   Newly created CFs should be shown in the first attribute group per default so that users need one step less to work with their custom field.
*   If they want to hide the field, or see it in another attribute group, they can still use the form configuration
