Filtering out Schedule

[nus-pe-bot]

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

Filtering out the schedule causes the dashboard to have the following issue:

It causes the dashboard to have empty upcoming schedules. I do not think that this is an intended behavior, as the list is supposed to provide upcoming schedules. This might be a high feature flaw as the main functionality of the upcoming schedule does not match the behavior itself.

---

_{[original: nus-cs2103-AY2122S1/pe-interim#4363] [original labels: type.FeatureFlaw severity.High]}

[kslui99]

Team's Response

Reason for rejecting:

• This bug was reported during the Part II (Evaluating Documents) stage of the PE.

Additional Info (in case there were any errors with the timestamp of this bug submission)

Reasons for rejecting:

• This is actually the expected and correct behaviour from the user's point of view. Imagine I'm on the Dashboard tab, and I see a long list of all upcoming events, but I only want to see my upcoming school events. I will run /schedule filter t/school. Our current product works correctly, because after running this /schedule filter t/school command, the Dashboard will indeed show only the upcoming school events, as expected by the user. As expected by the user, the irrelevant events that the user does not want to see will indeed be filtered away.
• This behaviour is intentional because it fits in with the whole point of the Dashboard tab, which is to aggregate/summarize the information from the other tabs, as mentioned in our User Guide (see screenshot below). The whole point of the Dashboard tab is to have a bird's eye view of the exact same information that you see on the other tabs. Hence, what you see on the Schedule tab (the filtered schedule) should be exactly the same as what you see on the Dashboard tab (the filtered schedule as well) and thus our product works correctly from the user's point of view.
• This behaviour is intentional also because it fits in with the whole point of providing convenience commands. One of the main benefits of us providing convenience commands is precisely for the user to make changes to another tab, for example the Schedule tab (for example filtering the events by typing /schedule filter t/school), while the user is on the Dashboard tab, and immediately see the changes synced to the Dashboard tab. So our current product works correctly as expected from the user's point of view.
• If instead we followed your suggestion, it will be disastrous for the user. This is what will happen if we followed your suggestion: Imagine I'm on the Dashboard tab. I run /schedule filter t/school. Nothing happens, nothing in the Dashboard changes. Following your suggestion will result in the wrong product behaviour.

Reasons for changing severity from High to Low:

• Even if you insist that this is a feature flaw, the severity cannot be High, because it does not cause a major problem or make the product almost unusable for the user. Instead, the severity should be Low, because all it takes for the user to fix the "empty upcoming schedules" in the Dashboard tab is a simple /schedule list command, which is only a minor inconvenience.

Screenshot of User Guide's description of Dashboard Tab:

Duplicate status (if any):

--