You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2020. It is now read-only.
We want to add the request messages that are created along with lesson requests to the user's chat inbox.
Overview
Problem statement
Right now, users are able to add messages to their requests. We want those messages to also be seen in the toUser's inbox (along with an automated message letting them know about that new request that it came from).
Proposed work
High-level overview of what we're building and why we think it will solve the problem.
Success criteria
The criteria that must be met in order to consider this project a success.
User stories
How the product should work for various user types.
User type 1
User type 2
Scope
Requirements
Current project requirements.
Future work
Future requirements.
Non-requirements
List anything that is out of scope.
Designs
Include designs here or add directly to the Requirements or User Stories sections.
Alternatives considered
List any alternatives you considered to this approach. Explain why they weren't used.
Related documents
Include links to other pages as necessary (e.g. technical design doc, project proposal, etc.)
The text was updated successfully, but these errors were encountered:
Add request messages to chat DMs
We want to add the request messages that are created along with lesson requests to the user's chat inbox.
Overview
Problem statement
Right now, users are able to add messages to their requests. We want those messages to also be seen in the toUser's inbox (along with an automated message letting them know about that new request that it came from).
Proposed work
High-level overview of what we're building and why we think it will solve the problem.
Success criteria
The criteria that must be met in order to consider this project a success.
User stories
How the product should work for various user types.
User type 1
User type 2
Scope
Requirements
Current project requirements.
Future work
Future requirements.
Non-requirements
List anything that is out of scope.
Designs
Include designs here or add directly to the Requirements or User Stories sections.
Alternatives considered
List any alternatives you considered to this approach. Explain why they weren't used.
Related documents
Include links to other pages as necessary (e.g. technical design doc, project proposal, etc.)
The text was updated successfully, but these errors were encountered: