• Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • 1.9.0
    • None
    • lightspeed, UI
    • None
    • Enable floating action button for Lightspeed
    • False
    • Hide

      None

      Show
      None
    • False
    • In Progress
    • RHDHPLAN-243 - [Lightspeed] Developer Lightspeed Chat Popup/Button
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • 67% To Do, 33% In Progress, 0% Done

      EPIC Goal:

      Enable developers to access a stateful, persistent Lightspeed chat window from anywhere in Red Hat Developer Hub through a Floating Action Button (FAB), allowing them to get quick assistance without breaking their workflow and ensuring all conversations are preserved in chat history.

       

      Why is this important ?

      • Users can seek help instantly from the FAB for lightspeed without leaving RHDH, increasing productivity
      • Stateful chat minimizes disruptions by letting users minimize and restore conversations at any time.
      • Aligns the Lightspeed chat experience with OpenShift Lightspeed for a cohesive ecosystem feel.
      • Ensures conversations are saved to chat history for later review, reinforcing trust in RHDH as a reliable development assistant.

       

      Acceptance Criteria

      • Lightspeed is accessible via FAB from any page within RHDH
      • Chat window supports overlay, docked, and full-screen modes per Figma. Users can toggle between overlay, docked, and full-screen modes seamlessly.
      • Chat window state (open/minimized/active chat) persists until explicitly closed.
      • All pop-up conversations are saved automatically to central Lightspeed history.
      • Left-hand navigation entry for Lightspeed is removed; FAB on the bottom-right acts as the primary access point.

              dsantra12 Debsmita Santra
              rorai Rohit Rai
              RHIDP - Frontend Plugins & UI
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: