• Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • 1.7.0
    • None
    • lightspeed
    • None
    • Add feedback mechanism to chat responses
    • False
    • Hide

      None

      Show
      None
    • False
    • Done
    • RHDHPLAN-39 - RHDH Lightspeed - Incorporate RHDH specific knowledge in responses [RAG]
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • Allow users to provide feedback to each chat response to indicate the correctness of the response

      Why is this important?

      • With the user feedback mechanism, it allows us to evaluate the correctness of our response as well as understanding the discrepancies based on the feedback based on the comment from the users. These data will help us to improve the responds by fine tuning the model and the documentation in the future

      Scenarios

      1. On the first time that the user install/use the Lighspeed plugin, they have an option to op-in or op-out of the feedback
      2. User make a query to ask question on the Lightspeed plugin
      3. The chat provides the response to the question
      4. Users can provide feedback on the UI (if the user selected to op-in to the feedback) to each chat response to indicate the correctness of the response in one of the following responses:
        • Thumbs up - user is satisfied with the response
        • Thumbs down - user is not satisfied with the response
          • Allow user to comment on the unsatisfied response to help us to improve the support in the future
      5. The feedback is collected and send back to our server for data collection and data analysis
      6. User can change the feedback op-in or op-out settings after the initial set up

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

              rh-ee-jdubrick Jordan Dubrick
              eyuen@redhat.com Elson Yuen
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: