🎨 [Frontend] Support Center: read/unread conversations #8489
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
odeimaiz
added
t:enhancement
odeimaiz
changed the title
odeimaiz
changed the title
There was a problem hiding this comment.
Pull Request Overview
This PR adds support for read/unread and resolved/open conversation states in the frontend support system. It introduces differentiated behavior between regular users and support members, with filtering capabilities and visual indicators.
- Refactors conversation models to use inheritance with
ConversationSupportandConversationProjectextending baseConversation - Adds filter buttons (All/Unread for users, All/Open for supporters) and read/resolved state management
- Implements conversation sorting by modification date and visual badges for status indication
Reviewed Changes
Copilot reviewed 12 out of 12 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
osparc/ui/list/ListItem.js |
Removes subSubtitle property and adds third-column layout support with MAX_ROWS constant |
osparc/support/SupportCenter.js |
Adds automatic read marking when users view conversations |
osparc/support/Conversations.js |
Implements filter buttons, conversation sorting, and state-based visibility |
osparc/support/ConversationPage.js |
Replaces appointment functionality with resolve case feature for supporters |
osparc/support/ConversationListItem.js |
Adds unread/resolved badges and restores subSubtitle handling locally |
osparc/support/Conversation.js |
Updates to use new ConversationSupport model |
osparc/study/ConversationPage.js |
Updates to use new ConversationProject model |
osparc/study/Conversation.js |
Updates to use new ConversationProject model |
osparc/store/ConversationsSupport.js |
Adds API methods for marking conversations as read/resolved |
osparc/data/model/ConversationSupport.js |
New specialized model for support conversations with read/resolved states |
osparc/data/model/ConversationProject.js |
New specialized model for project conversations |
osparc/data/model/Conversation.js |
Refactored as abstract base class with common conversation functionality |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
services/static-webserver/client/source/class/osparc/data/model/ConversationSupport.js
Outdated
Show resolved
Hide resolved
services/static-webserver/client/source/class/osparc/support/ConversationPage.js
Outdated
Show resolved
Hide resolved
…onversationPage.js Co-authored-by: Copilot <[email protected]>
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 22 out of 22 changed files in this pull request and generated 2 comments.
Comments suppressed due to low confidence (1)
services/static-webserver/client/source/class/osparc/support/ConversationListItem.js:1
- Array index order is incorrect: after sorting messages by date (oldest first), the first message should be at index 0 and the last message should be at the end of the array. The current assignment is backwards.
/* ************************************************************************
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
services/static-webserver/client/source/class/osparc/data/model/ConversationSupport.js
Outdated
Show resolved
Hide resolved
services/static-webserver/client/source/class/osparc/support/Conversations.js
Show resolved
Hide resolved
…l/ConversationSupport.js Co-authored-by: Copilot <[email protected]>
…mcore into enh/conversation-read
odeimaiz
requested review from
GitHK,
bisgaard-itis,
giancarloromeo,
matusdrobuliak66,
pcrespov and
sanderegg
…mcore into enh/conversation-read
|
GitHK
approved these changes
Oct 14, 2025
giancarloromeo
approved these changes
Oct 14, 2025
sanderegg
approved these changes
Oct 14, 2025
This was referenced Oct 28, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
This PR adds support for read/unread conversation states in the frontend. It introduces differentiated behavior between regular users and support members, with filtering capabilities and visual indicators.
Related issue/s
How to test
Dev-ops