✨ [Frontend] OEC to Support chat

[odeimaiz]

What do these changes do?

As suggested by @pcrespov, when an OEC is shown on a Flash Message, if the Support feature is enabled, instead of providing the copy OEC&Context to clipboard button, this PR gives provides the users with a quick way to contact support.

When the user presses the contact support button, a "provide more context" window pops up where the user can provide more context. This is then added to the curated OEC&Context and posted as a new Support conversation.

Related issue/s

• related to https://github.com/ITISFoundation/private-issues/issues/303

How to test

Dev-ops

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 8f7a815.

🟢 All jobs passed!

But CI Insights is watching 👀

[Copilot]

Pull Request Overview

This PR adds support for contextual chat integration in the OEC (osparc Error Center) flash messages, allowing users to either copy error context or directly open a support chat with the error details.

• Creates a new FlashMessageOEC class that extends FlashMessage with chat and copy functionality
• Modifies FlashMessenger to use the new OEC flash message for errors with support IDs
• Updates support center UI to show "Ask a question" button for all users and changes "Support ID" to "Ticket ID"

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

File	Description
FlashMessageOEC.js	New flash message component with copy-to-clipboard and chat support functionality
SupportCenter.js	Removes conditional display of "Ask a question" button
ConversationPage.js	Changes label from "Support ID" to "Ticket ID"
FlashMessenger.js	Refactors error handling to use new OEC flash message class and extracts common flash message addition logic

[pcrespov]

Suggestions:

• Instead of showing raw JSON, format and send a clear formatted message, for example:

  Hi,
  
  I got this error: {message}
  
  - SupportID: 1234
  - Date: 2023-04-34
  - ...
  

• After sending the first message, place the cursor in a new draft message so the user can continue writing.
  • Can you delete/edit a sent message? If so the user could also modify the default message
• Keep in mind: the error could be critical (e.g. a service outage). In that case, the support channel might not be functional. If so, fall back to the previous copy-to-clipboard approach.

[GitHK]

Very nice feature!
One proposal, which I think it might improve it's usefulness by a big margin.
In an effort to avoid having no additional context messages, I would ask the user to provide some context message before sending this report over. A popup where they add more context would be great. When they press send on the popup, it will open the support chat with the message already sent (already containing the error).

[matusdrobuliak66]

💯

[pcrespov]

Please check my suggestsions

[odeimaiz]

@pcrespov @GitHK I went for a mix of what you requested. Check the updated description and animation.

[pcrespov]

very nice! much better.
Thx

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[GitHK]

Way better! Thanks for enhancing it!