Skip to content

User Story #18 - Saving Summaries #3

@irenfro

Description

@irenfro

Description

As a user, I would like to save my summaries to a database.

Tasks

  • Send the summary to the Database
  • Test the data stored in Database
  • Create documentation adding data to database
  • Implement save button and component to view the corresponding updated list of summaries
  • Create endpoint to add user’s notes in the database
  • Create documentation for adding user's notes in the database
  • Test the added notes data in the database
  • Create endpoint for the list of user's notes in the database
  • Create documentation for the list of user’s notes in the database
  • Test the list of user’s notes in the database

Acceptance Criteria

  • Given that the summary is added to the Database correctly and tested properly, when implemented then it will be simple for us to access the summary data upon a user’s request.
  • Given well-written documentation for sending data to the database, when we wish to send data, there will be clear and easy to read instructions on how to utilize them
  • Given that the user saves a summary, the frontend will respond with correct error/success messages.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions