**As** a project manager that is working according to PM²/PMflex
**I want to** have a gui to select project attributes to add them to wiki
**so that** easily add project attributes to agenda items

**Acceptance criteria**

* Begin of the insertionThe project attribute macros `projevtValue:foo` in the ckEditor are enhanced by automatically changing to display the value they contain (similar to how it was done recently for WP links which also directly translate to their displayed value)End of the insertion Begin of the deletion There is a wiki macro `Project Attribute`End of the deletion

* The Begin of the insertion"+ Insert" of the ckEditor menu gets a new option "Project attribute"

End of the insertion Begin of the deletion content is shown as WYSIWYG

End of the deletion * Begin of the insertionClicking that, opens a dialog where the user can select which attribute to show

* ItEnd of the insertion Begin of the deletion ThereEnd of the deletion is Begin of the insertiona single select

* _Open: How should this dialog look like?_

* After selectingEnd of the insertion an Begin of the insertionattribute from the dialog, it gets rendered (in display mode) in the current cursor position within the ckEditor 

* When saving the whole editor and switching itEnd of the insertion Begin of the deletion optionEnd of the deletion to Begin of the insertiondisplay mode,End of the insertion Begin of the deletion startEnd of the deletion the Begin of the insertionmacro gets replaced by an InplaceEditField, allowing users with certain permissions to edit it directlyEnd of the insertion Begin of the deletion editing processEnd of the deletion

* Renaming a project attribute does not break the macro integration.


Begin of the insertion**Out of scope**

* Nested inplaceEditFields don't have to work. They can be read-only when the project attribute is rendered within another inplaceEdit field,

* e.g the angular inplace edit fields (like the WP description)

* e.g. using the macro within the project description


End of the insertion **Permissions and visibility considerations**

* We keep the existing permission scheme.