Content
View differences
Updated by Jens Ulferts about 5 years ago
**Before starting on this, usage **As** a _\[enter role of formly needs to be decided upon.** user\]_
**I want to** _\[enter objective\]_
**so that** _\[enter desired result\]_
Please also take the parent work package
##36382
into account.
**Acceptance criteria**
* Project settings rendered in Angular/formly _\[enter acceptance criteria\]_
* Render the project widgets also via formly
#### Out of scope
* Adding the multi select custom fields (#36513 and <mention class="mention" data-id="36511" data-type="work_package" data-text="#36511">#36511</mention> )
#### 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\]_
Please also take the parent work package
##36382
into account.
**Acceptance criteria**
* Project settings rendered in Angular/formly
* Render the project widgets also via formly
#### Out of scope
* Adding the multi select custom fields (#36513 and <mention class="mention" data-id="36511" data-type="work_package" data-text="#36511">#36511</mention> )
#### 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.