search

hcs1203 / pe

0 stars 0 forks source link

bprio is not needed #10

Open hcs1203 opened 1 year ago

hcs1203 commented 1 year ago

bprio is not needed since bedit 3 prio/____ does the same anyway

nus-pe-script commented 1 year ago

Team's Response

Indeed, we could have made the rationale behind the bprio and sprio commands more explicit in the UG. However, the rationale was explained in the DG which was to make it easier for users to change the priority level of clients without having to use the bedit or sedit commands, since priority levels are dynamic and tend to change more often than buyer or seller fields, and hence bprio and sprio would act as a convenient shortcut to achieve this change. Therefore, we would be rejecting this as a feature flaw. Screenshot 2023-11-19 at 4.23.41 PM.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: While I appreciate this difference, maybe you can remove the priority from the edit field? This can make the edit field more catered to the more serious/important/rarely used feature while the _prio fields can be used solely for editing priorities. This can ensure that there is no overlap between the 2 functions and the user doesn't accidentally touch any of the other features when changing priorities.