- Issue created by @grzegorz.bartman
k.wiktorowicz → made their first commit to this issue’s fork.
- 🇵🇱Poland michalmagdziarek
michalmagdziarek → made their first commit to this issue’s fork.
- 🇵🇱Poland sebastian.langierowicz
sebastian.langierowicz → made their first commit to this issue’s fork.
-
sebastian.langierowicz →
committed ca07161f on 1.x authored by
michalmagdziarek →
Resolve #3524317 "Must read flagging feature"
-
sebastian.langierowicz →
committed ca07161f on 1.x authored by
michalmagdziarek →
- 🇵🇱Poland grzegorz.bartman
I've tested the Must-Read Flagging Feature implementation and found two important issues that need to be addressed:
Issue 1: Content Editor Role Access Problem
Users with the "content editor" role cannot access the summary views that show who has read and who hasn't read the flagged content. This is a critical functionality gap since content editors are typically the users who need to monitor reading compliance for mandatory content.
Issue 2: Button Styling Inconsistency
The "mark as read/unread" button currently has basic styling that doesn't match the visual design of other action buttons in the system. For better user experience and visual consistency, this button should use similar styling to the "read more" button found on the /news page.
Issue 3: Field Scope Too Broad
The
field_mark_as_must_read
field has been added to multiple content types (article, document, event, knowledge_base_page, page, webform), but according to the requirements, this field should only be available for the "news article" content type (node/add/article). The current implementation adds unnecessary complexity and potential confusion by making this field available on content types where it's not needed.Additional details:
- The permission issue affects the core functionality for content editors who are responsible for tracking reading compliance
- The styling issue impacts user experience and visual consistency across the intranet
- The field scope issue adds unnecessary complexity - the must-read functionality should be limited to news articles only
- All issues were discovered during user acceptance testing with actual content editor accounts
Suggested fixes:
- Review and adjust permissions for the "content editor" role to include access to must-read tracking views
- Update the CSS styling for the read/unread toggle button to match the existing "read more" button design pattern
- Remove the
field_mark_as_must_read
field from all content types except "article" (news articles) to match the original requirements
These issues should be addressed to ensure the feature is fully functional for its intended users and maintains design consistency within the OpenIntranet system.
- Merge request !27#3524317: Functionality improvements to Must Read as per comment 8 → (Merged) created by k.wiktorowicz
-
k.wiktorowicz →
committed 77b791a1 on 1.x
#3524317: Functionality improvements to Must Read as per comment 8
-
k.wiktorowicz →
committed 77b791a1 on 1.x
- Merge request !40#3524317: Removal of the “Must Read” checkbox from content types other than “News Article”. → (Merged) created by k.wiktorowicz
-
k.wiktorowicz →
committed 5c049d3d on 1.0.x
#3524317: Removal of the “Must Read” checkbox from content types other...
-
k.wiktorowicz →
committed 5c049d3d on 1.0.x