nighoggDatatype / pe

0 stars 0 forks source link

Unclear when a book is 'overdue' #1

Open nighoggDatatype opened 3 years ago

nighoggDatatype commented 3 years ago

Nowhere in the UG is it stated when a book is considered overdue. Is it hard-coded, or can it be customized in some setting somewhere, or could it be different between users, perhaps with longer registered, and higher activity borrowers being more trustworthy of longer borrowing times?

nus-pe-bot commented 3 years ago

Team's Response

No response provided.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

It is currently not possible to set the policy for how long until a book is considered overdue

There is currently no command explicitly to set the default time until a book is considered overdue. SumatraPDF_vNcUgY5m45.png

There is also no known feature to set any sort of deadline for a book to be returned by, so it is likely hard coded as far as I can tell. SumatraPDF_3kXfC9zc1B.png

If such a feature does exist, it is already too difficult to discover, since if it is neither a stand-alone command, or part of the 'borrow' command, or part of a non-existant 'settings' command, there are no more obvious places to set it.


[original: nus-cs2103-AY2021S2/pe-interim#1973] [original labels: severity.Medium type.FeatureFlaw]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

This is not a bug. We will be engaging our client with regards to the amount of time before each book would be considered to be overdue, which will be predetermined by our very first contact with the client.

By preventing the client from being able to access the amount of time before each book is considered to be overdue, this would also help to prevent the occurrence of unnecessary complications in the borrowing process, e.g. the client setting a wrong overdue date for a book, or accidentally deleting the overdue date of a book.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your reason]


:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your reason]


:question: Issue type

Team chose [type.FeatureFlaw] Originally [type.DocumentationBug]

Reason for disagreement: [replace this with your reason]


:question: Issue severity

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

Reason for disagreement: [replace this with your reason]