Content
Epic DREAM-745: Simplify selection, creation and usage of project and work package attributes macros
View differences
Updated by Henriette Darge 14 days ago
**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**
* The project attribute macros `projectValue:foo` `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)
* The "+ Insert" of the ckEditor menu gets a new option "Project attribute"
* Clicking that, opens a dialog where the user can select which attribute to show
* It is a single select
* _Open: How should this dialog look like?_
* After selecting an attribute from the dialog, it gets rendered (in display mode) in the current cursor position within the ckEditor
* When saving the whole editor and switching it to display mode, the macro gets replaced by an InplaceEditField, allowing users with certain permissions to edit it directly
* Renaming a project attribute does not break the macro integration.
**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
**Permissions and visibility considerations**
* We keep the existing permission scheme.
**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**
* The project attribute macros `projectValue:foo`
* The "+ Insert" of the ckEditor menu gets a new option "Project attribute"
* Clicking that, opens a dialog where the user can select which attribute to show
* It is a single select
* _Open: How should this dialog look like?_
* After selecting an attribute from the dialog, it gets rendered (in display mode) in the current cursor position within the ckEditor
* When saving the whole editor and switching it to display mode, the macro gets replaced by an InplaceEditField, allowing users with certain permissions to edit it directly
* Renaming a project attribute does not break the macro integration.
**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
**Permissions and visibility considerations**
* We keep the existing permission scheme.