Epic Goal

• The backend work for the LightSpeed chat plugin backend to support chat persistence
  • Persistent storage for the chat plugin
  • Chat is authenticated for access by individual user only, e.g. by RBAC authentication
  • API for UI to access the chat session with the chat history
  • API for UI to create, load and delete the chat session
  • Configurable auto expiration of the chat session that delete the history of a given chat session
  • Security consideration for handling PII data stored as part of the chat history
• The backend work for the LightSpeed chat plugin backend to support multiple chats simultaneously
  • Chat is authenticated for access by individual user only, e.g. by RBAC authentication
  • Session ID assigned for each unique chat session for create, load and deletion of chat sessions

Why is this important?

• …

Scenarios

1. ...

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):

1. …

Open questions::

1. …

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