Workflow of adding sessions and then users to sessions may not make sense

[JoelHo]

As I understand it, the workflow for adding a session is:

• add_session d/day t/t to t su/sub
• list persons
• scroll and find relevant tutors and students
• alternatively, find relevant tutors and students first, then add_session
• assign s/id...c/id t/id
• view_session c/id (if necessary to verify)

For the various reasons below, this may not make sense

• complex multi-step workflow
• have to keep some ids in memory or copy into a text file (which defeats the point?)
• have to change views
• session may not necessarily make sense without a tutor or student, since these are largely dictated by tutor and student schedules

This workflow is quite annoying to use in practice, anecdotally.

[nus-pe-bot]

Team's Response

For tuition centers, we consider the possibility of them wanting to create the session first before finding an available tutor or assigning students.

As for the finding of a person, there is the find command.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: In my opinion, a session does not make sense without tutors and students, as it represents a timeslot. Without students or tutors, this has no meaning and may be accidentally added by a user, leading to the user potentially thinking there is an activity scheduled for that timing.

As mentioned by the team, there is the find command, however, the find command only lets me filter by name, which is not relevant to scheduling sessions (because we don't schedule people by their name, rather by subject/time/location/tags/etc)

---