search

nus-cs2103-AY2324S1 / forum

10 stars 0 forks source link

Feature Flaw Indirectly included in Planned Enhancement, but is still problematic #521

Closed lihongguang00 closed 9 months ago

lihongguang00 commented 9 months ago

Hi Prof,

Bug Report Link

The bug report in question is a feature flaw. The current state of feature that I believe is flawed uses GUI buttons rather than keyboard (with no other alternative), which is makes it not keyboard friendly. However, in one of the Planned Enhancement, they did mention adding CLI based commands that would indirectly address this feature flaw. However, my original argument was more of that the team has had their priorities wrong (since they could have spent the time implementing the GUI button into adding a listener to the GUI for keyboard support instead), and I was wondering if this would violate the module's PE guidelines if I were to reject their response (which they rejected the bug report), since it is technically addressed to some degree?

Thanks!

damithc commented 9 months ago

@lihongguang00 The planned enhancement sections gives immunity even for cases that should be in scope of the current version (that's why that list is restricted in size). If a feature flaw is of lower priority, it doesn't need to be put it in the planned enhancement section because such feature flaws can be categorized as NotInScope, and escape the penalty that way.

lihongguang00 commented 9 months ago

@damithc ah, I see, understood prof, thank you!