Open weiseng18 opened 4 days ago
[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
We accept the bug. However, we believe that this will not be a frequent occurrence as once the user manages to use markpaid as a workaround once, they will be able to use it again without problem the next time. We believe that using markpaid is an intuitive workaround to correct the error, we didn't mention it in the UG.
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: [replace this with your reason]
If the user makes a mistake in "Logging fees" they might want to reverse the changes made in this step. There is no corresponding "remove fees" function, and also specifying a negative value is not permitted by the application.
Perhaps using the "Mark paid" function might be good enough to fix any error, but the user might not be tech-savvy, and even if they are, they might be worried whether doing so has other side effects.
If the above is the intended workaround to fix errors made by user, then this is a
DocumentationBug
. Otherwise it becomes aFeatureFlaw
since the only other way I can imagine the user fixes this, is by deleting the student and re-entering everything they had so far.severity.Medium
because it can cause quite some inconvenience, but only if a mistake was made