search

jbkim1999 / pe

0 stars 0 forks source link

Should be able to add a past schedule #5

Open jbkim1999 opened 2 years ago

jbkim1999 commented 2 years ago

image.png

To begin with, this is not specified in the UG.

Additionally, since archive view is supported, it makes sense to support addition of a past schedule for record purposes.

This would be instance of feature flaw (perhaps overzealous input parsing)

nus-pe-bot commented 2 years ago

Team's Response

Although this is not specified in the UG, users can be informed of this detail using this error message. This reason is rejected because "Nitty-gritty details missing from the UG is not a bug long as the user is informed of those details using other means such as error messages or in-app help."

Moreover, archive view is supported because schedules are displayed in chronological order, so expired schedules might block users' view of recent schedules. Hence, all expired schedules are automatically archived. Lastly, the addition of past data is not so useful in our concerns as the rationale for the schedule is for users to keep track of future events instead of recalling past events.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: "the rationale for the schedule is for users to keep track of future events instead of recalling past events."

I do not agree with this statement. Firstly, this rationale can't be found anywhere in the UG, nor the DG.

As a trainer, I might wish to add in past schedules just to know what trainings / matches have been done to the team / player. This is crucial to gauge the exhaustion level of the players overall. The benefits of allowing past schedules are quite a lot.

Secondly, if recalling past events is not the goal, then I question the need of the archive command, which allows viewing of the past schedules. The archive command then becomes detached from the supposed rationale.

Lastly, from the website, "It is better to warn rather than to block when inputs are not compliant with the expected format." Hence I still believe this is a feature flaw.

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Low]

Reason for disagreement: "the rationale for the schedule is for users to keep track of future events instead of recalling past events."

I do not agree with this statement. Firstly, this rationale can't be found anywhere in the UG, nor the DG.

As a trainer, I might wish to add in past schedules just to know what trainings / matches have been done to the team / player. This is crucial to gauge the exhaustion level of the players overall. The benefits of allowing past schedules are quite a lot.

Secondly, if recalling past events is not the goal, then I question the need of the archive command, which allows viewing of the past schedules. The archive command then becomes detached from the supposed rationale.

Lastly, from the website, "It is better to warn rather than to block when inputs are not compliant with the expected format." Hence I still believe this is a feature flaw.