# Feature OP-20131 - Add multiselection and mandatory indicators in form configuration page

Project: OpenProject
Status: rejected
URL: https://community.openproject.org/work_packages/OP-20131

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 / Work package administration, Frontend components and Primer design system |
| 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 changing the form configuration of a type  
**I want to** quickly see some characteristics of the fields being added  
**so that** I can better understand the fields being manipulated, and detect if something is wrong

**Acceptance criteria**

*   On &quot;Form configuration&quot; page of a type
    
    *   Indicate when a field has multi-selection enabled. It already indicates the type (User, Version, List, etc). It would be useful to also indicate multi or not
        
    *   Indicate when a field is mandatory. A little asterisk next to the name, same as in the form configuration, could be enough.
