✨ [Frontend] Support center

[odeimaiz]

What do these changes do?

This is the first frontend iteration on the Support Center and checks all the request defined in Priority 1:

• "Support" button is visible in the top navigation bar. Visible only if a support group is configured in product settings.
• Clicking "Support" opens a side panel with:
  • List of support conversations:
    • Regular users will only see their messages.
    • User that belong to the Support group will see all support conversations coming from all users
    • Each conversation item includes:
      • Avatar of the last user writing
      • Title or snippet of the last message
      • Username of the last message
      • Timestamp of the last message
  • "Ask a Question" flow includes:
    • Create new conversation (when the first message is written)
    • “Share Project” checkbox if a project is open
    • Automatic metadata attachment:
      • deployment
      • product
      • (project_id)

It also implements:

• A way to open directly a conversation for a given link: ${deployment}/#/conversation/${conversation}

Missing:

• RT chat: listen to WS events

User requesting support:

A Support user, supporting:

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 3df29d3.

✅ Passed Jobs With Interesting Signals

Pipeline	Job	Signal	Health on base branch	Retries	🔍 CI Insights	📄 Logs
CI	unit-tests	Base branch is broken, but the job passed. Looks like this might be a real fix 💪		0	View	View

[matusdrobuliak66]

Thanks! 👍

But @odeimaiz @calys while looking into Fogbugz, I realized and I think it would be better call to stick with a single ticket system. We could simply let users create a Fogbugz case directly from the web platform (which would still include for example sharing the project with support option), and then handle all communication and ticket state management there in the Fogbugz via emails. I know right now, we agreed to create a Fogbugz case when a conversation starts, but questions pop up - like how support is notified when users reply later/next day, or how cases get closed. This feels like we’re going at some point to re-implement a ticketing system and, worse, having to keep it in sync with Fogbugz which is our real ticketing system to communicate with users.

[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

[odeimaiz]

@mergify queue

[mergify]

queue

🟠 Waiting for conditions to match

• -closed [📌 queue requirement]
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • label=🤖-automerge
    • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
    • #approved-reviews-by>=2
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0
    • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
    • #review-threads-unresolved=0
    • -conflict
    • -draft
    • base=master
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • label!=🤖-do-not-merge
    • any of: [🛡 GitHub branch protection]
      • check-skipped = deploy to dockerhub
      • check-neutral = deploy to dockerhub
      • check-success = deploy to dockerhub
    • any of: [🛡 GitHub branch protection]
      • check-success = system-tests
      • check-neutral = system-tests
      • check-skipped = system-tests
    • any of: [🛡 GitHub branch protection]
      • check-success = unit-tests
      • check-neutral = unit-tests
      • check-skipped = unit-tests
    • any of: [🛡 GitHub branch protection]
      • check-success = check OAS' are up to date
      • check-neutral = check OAS' are up to date
      • check-skipped = check OAS' are up to date
    • any of: [🛡 GitHub branch protection]
      • check-success = integration-tests
      • check-neutral = integration-tests
      • check-skipped = integration-tests
    • any of: [🛡 GitHub branch protection]
      • check-success = build-test-images (frontend) / build-test-images
      • check-neutral = build-test-images (frontend) / build-test-images
      • check-skipped = build-test-images (frontend) / build-test-images
    • any of: [🛡 GitHub branch protection]
      • check-success = SonarCloud Code Analysis
      • check-neutral = SonarCloud Code Analysis
      • check-skipped = SonarCloud Code Analysis
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed