emotion-records

[Xristof23]

Value proposition

As a user I want to see an overview of my recorded emotion entries on a separate page In order to have a well structured and complete journal of all my recorded emotions over time.

Description

Acceptance criteria

• [ ] Users can view the recorded emotions as a list on a separate page by clicking on a button on the main page, each entry showing date and time, in order from new to old entries
• [ ] If more details are available, Users can toggle a details view of an entry by clicking on it
• [ ] On the emotion records page there is a button which directs the user back to the tension entry page

Tasks

• [ ] Create and switch to a new feature branch feature/emotion-records
• [ ] Move the list of emotion entries from index.jsto newly created pages/emotion-records.js
• [ ] Create a new component EmotionRecordsList which renders a list of all emotion entries
• [ ] Sort respective li-items from newest to oldest entry
• [ ] Add functionality to the EmotionRecordsList to toggle a view of the tension level of an entry by clicking the respective li-item
• [ ] Add a Link on pages/emotion-records.js to pages/Index.js
• [ ] Add a Link on pages/Index.js to pages/emotion-records.js
• [ ] Add minimal styling to new elements

[FelineHuhn]

Good work team, everything clear formulated in a good structure 🥳

I would to suggest to split this user story into two: As your value proposition is mentioning the benefit "I want to see an overview of my recorded emotion entries", a details view should not be another benefit, or? The details view of every tension level could be an own user story instead.

One question: You implement buttons here and not a application-wide navigation, or? A button to navigate to the emotion records page, when the user is on the emotion records page doesn't make much sense... Also the user cannot navigate back to the main page from the emotion records page, but only to the seven emotions page, or? Better think about again, on which page you need which button (and which not). After that you need to adapt the tasks accordingly.

Another point is, since you already have an overview of the tension levels in the user story before, the value proposition should emphasize that it should be shown on a separate page for clarity (or something similar to it, because the overview list is already visible before).

Keep up the great work 🚀

[FelineHuhn]

Great improvement of the value proposition and also the button issue 👏👏

Ahhh now I understand, the tension level is only shown on button click on the date&time entry, yes? Maybe you should implement a toggle functionality, so that the user can click it away again, or? The way it is described now, the details are only displayed and then remain displayed. When it should be toggled, you can leave the wireframe as it is and just add it in the acceptance criteria and formulate a task for it.

In tasks I noticed something new: Since others, which are not team members of your capstone project, will review your user stories, code etc. it would be more understandable to rename your "list" (as you call it in the tasks and also "list page" in the acceptance criteria) to something like emotion records list. And maybe think about to create a EmotionRecordsList component to render your "list", or did you plan it and not list it here?

[FelineHuhn]

Ready to work on 🚀🚀