# Feature SSI-185 - Custom field creation with drop down selector

Project: Stream Storage Integrations
Status: rejected
URL: https://community.openproject.org/work_packages/SSI-185

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| 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 | https://www.figma.com/design/oTMDTvcwrx35qExTkkSKBn/Custom-fields?node-id=1396-20062&p=f&t=svGD5xV2bGMr6pdB-0 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| 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  
**I want to** have a simple way to create custom fields  
**so that** configuration of the custom fields can happen after creation.

**Acceptance criteria**

*   The custom field index page must contain a button action to create custom fields by selecting the correct format from a dropdown.
    
*   Selecting a format for creation, a custom field of this format must be created and the user must get redirected to the "Edit custom field" page (Details tab).
    
*   The custom field is created with the name "New custom field"
    
    *   If the name "New custom field" is already taken, the name is amended with an increasing number in parenthesis (i.e. "New custom field (1)", "New custom field (2)", etc.)
        
*   The custom field is created with the default configuration for this format and type.
    
*   If no enterprise edition is active, the custom field format hierarchy must have an enterprise icon behind the option label.
    
    *   If the admin still selects the hierarchy format option, it gets redirected to a full view enterprise upsale page.