Content
View differences
Updated by Parimal Satyal about 2 years ago
### Acceptance criteria
* The project overview will maintain the current implementation of widgets but include a new right pane (like in the Meetings module)
* This pane will display project attributes enabled for this project in their respective sections, along with their values (visible setting is respected, only admins can see/edit "invisible" project attributes)
* A section is only shown if at least one project attribute from that section is enabled for the project (if that number is zero, the section is hidden entirely)
* If the user has the permission "edit\_project", each section shows an edit icon
* Clicking this icon opens a dialog showing inputs for all enabled project attributes contained in that section
* Saving this dialog automatically closes the dialog and the changes are reflected in the sidebar without a browser page refresh
* If an invalid value was entered, the dialog is not closed and form validations are displayed (standard Primer style)
* Thee dialog **cannot** be saved if a project attribute value _within_ this section is invalid
* The dialog **can** be save if all project attributes WITHIN this section are valid
* Each section is self-contained. If a project attribute in section "A" is in an invalid state, a section "B" can still be saved.
* For example, if a new required project attributes is added to section "A". section "A" is now technically in an invalid state. However, this does not affect Section "B", which can be edited and saved normally.
* Special renderings in the sidebar:
* If a value is not set for a project attribute, "-" is shown
* Boolean fields are rendered with Yes/No
* Users are shown with their avatar
* Rich text values
* are properly formated (e.g. bold text is shown as bold...)
* are truncated when they are longer than 100 characters
* An "Expand" link opens a dialog showing the complete rich text value as read-only (similar to #52127)
* Multi user values are shown in a list
* Other multi values are shown comma-seperated
* If a project has no enabled project attributes, the sidebar is completely empty.
* A separate feature will address this blank state.
* ~~\[TBD\] \[TBD\] For project admins with permission to edit project attributes, there is a third More (...) button on the top right corner to the right of Add (+) with two options:~~ options:
* ~~"Manage "Manage project attributes" (redirects to Project settings > Project attribtues)~~ attribtues)
* ~~"Archive project"~~ "Archive project"
* URL routing: `projects/{project_id}`
* Accessible to project members with the permission "view\_project"
* Edit actions only available for project members with the permission "edit\_project"
* The project overview will maintain the current implementation of widgets but include a new right pane (like in the Meetings module)
* This pane will display project attributes enabled for this project in their respective sections, along with their values (visible setting is respected, only admins can see/edit "invisible" project attributes)
* A section is only shown if at least one project attribute from that section is enabled for the project (if that number is zero, the section is hidden entirely)
* If the user has the permission "edit\_project", each section shows an edit icon
* Clicking this icon opens a dialog showing inputs for all enabled project attributes contained in that section
* Saving this dialog automatically closes the dialog and the changes are reflected in the sidebar without a browser page refresh
* If an invalid value was entered, the dialog is not closed and form validations are displayed (standard Primer style)
* Thee dialog **cannot** be saved if a project attribute value _within_ this section is invalid
* The dialog **can** be save if all project attributes WITHIN this section are valid
* Each section is self-contained. If a project attribute in section "A" is in an invalid state, a section "B" can still be saved.
* For example, if a new required project attributes is added to section "A". section "A" is now technically in an invalid state. However, this does not affect Section "B", which can be edited and saved normally.
* Special renderings in the sidebar:
* If a value is not set for a project attribute, "-" is shown
* Boolean fields are rendered with Yes/No
* Users are shown with their avatar
* Rich text values
* are properly formated (e.g. bold text is shown as bold...)
* are truncated when they are longer than 100 characters
* An "Expand" link opens a dialog showing the complete rich text value as read-only (similar to #52127)
* Multi user values are shown in a list
* Other multi values are shown comma-seperated
* If a project has no enabled project attributes, the sidebar is completely empty.
* A separate feature will address this blank state.
* ~~\[TBD\]
* ~~"Manage
* ~~"Archive project"~~
* URL routing: `projects/{project_id}`
* Accessible to project members with the permission "view\_project"
* Edit actions only available for project members with the permission "edit\_project"