Content
View differences
Updated by Jens Ulferts about 5 years ago
Please also take the parent work package **As** a _\[enter role of user\]_
**I want to** _\[enter objective\]_
**so that** _\[enter desired result\]_
##36382
into account.
**Acceptance criteria**
* Multi select custom fields displayed and editable within the project settings _\[enter acceptance criteria\]_
* Multi select custom fields displayed and editable within the project details widget
#### Out of scope
* Changing the whole form to angular/formly (see <mention class="mention" data-id="36512" data-type="work_package" data-text="#36512">#36512</mention> )
* Implementing the backend (see #36511)
#### Open
* Is all the information required for the buttons available via the API? If not, should it be added or should that part still be rendered via Rails?
* How to handle the identifier? Currently changing it opens a second form which warns about the consequences. We could leave it at that and also reuse the existing rails based form for it. _..._
**I want to** _\[enter objective\]_
**so that** _\[enter desired result\]_
##36382
into account.
**Acceptance criteria**
* Multi select custom fields displayed and editable within the project settings
* Multi select custom fields displayed and editable within the project details widget
#### Out of scope
* Changing the whole form to angular/formly (see <mention class="mention" data-id="36512" data-type="work_package" data-text="#36512">#36512</mention> )
* Implementing the backend (see #36511)
#### Open
* Is all the information required for the buttons available via the API? If not, should it be added or should that part still be rendered via Rails?
* How to handle the identifier? Currently changing it opens a second form which warns about the consequences. We could leave it at that and also reuse the existing rails based form for it.