**As** a administrator of OpenProject
**I want to** be able to manage custom fields with ease
**so that** my instance of OpenProject works for its users

**Acceptance criteria**

* Primerize Begin of the insertionthe Admin/CustomEnd of the insertion Begin of the deletion CustomEnd of the deletion Field forms Begin of the insertionwhich were not primerized yet

End of the insertion Begin of the deletion - this is a placeholder.
 more details TBC


**Technical notes**

End of the deletion * Begin of the insertionFor Fields of type &quot;List&quot;, there will be a separate tab &quot;items&quot; (like for hierarchyEnd of the insertion Begin of the deletion <br>


**PermissionsEnd of the deletion and Begin of the insertionweigthed item lists)

End of the insertion Begin of the deletion visibility considerations**

End of the deletion * Begin of the insertionThe tab shows the current options table asEnd of the insertion Begin of the deletion _To whom is this feature visible?_

* _When isEnd of the deletion it Begin of the insertionis


**Technical notes**End of the insertion Begin of the deletion not visible?_


**Translation considerations**End of the deletion

* Begin of the insertion&nbsp;We plan to migrate the list fields into the hierarchy fieldsEnd of the insertion Begin of the deletion _Key termsEnd of the deletion and Begin of the insertioncan then useEnd of the insertion Begin of the deletion phrases inEnd of the deletion the Begin of the insertionexisting components on the items tab. Therefore it makes no sense to invest time into primerizing the current options table.End of the insertion Begin of the deletion key languages_ End of the deletion


Begin of the insertion**Permissions and visibility considerations**End of the insertion Begin of the deletion **Out of scope**End of the deletion

* Begin of the insertionAdmin-onlyEnd of the insertion Begin of the deletion <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._End of the deletion