search

LuYiting0913 / pe

0 stars 0 forks source link

Missing important use stories #15

Open LuYiting0913 opened 1 year ago

LuYiting0913 commented 1 year ago

image.png

missing stories like unassign task, sort task by deadline (as mentioned in UG)

soc-pe-bot commented 1 year ago

Team's Response

Severity of bugs related to missing requirements (e.g., missing user stories)? Depends on the potential damage the omission can cause. Keep in mind that not documenting a requirement increases the risk of it not getting implemented in a timely manner (i.e., future developers will not know that feature needs to be implemented).

Although we admit that we missed out certain user stories, we believe that this does not cause any damage to the developments. In addition, the user stories are based on the prior plan. Unassign command and sort by deadline are extra features we implemented since we have extra time to do so. Thank you for catching this bug.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: No actual damage caused cannot justify leaving important user stories out. (I still believe the user storied omitted are very important) There are still potential damage the omission CAN cause. "Keep in mind that not documenting a requirement increases the risk of it not getting implemented in a timely manner (i.e., future developers will not know that feature needs to be implemented)"

Moreover, the user stories should also be updated should there be a decision to add more functionalities.

:question: Issue severity

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

Reason for disagreement: "Only cosmetic problems should have this label" But this is not just a cosmetic bug. this can cause potential harm to the development of the project,