Open nus-se-script opened 1 week ago
Thank you for your suggestion! After carefully considering your point, the team felt that there is very little use to mass delete based on range. This is because the clients are not sorted in any particular order, unless you have filtered the client by name or phone number etc, to which there is very little correlation between these fields and them being mass deleted from Prudy. As such, there is really not much of a use case for such a function. Regardless, it is something that the team may consider in the future, provided a more concrete use scenario is provided (the tester did not provide an example for when such a function is required), and hence we choose to classify this bug as NotInScope
.
Furthermore, for how rare such scenarios are required (as explained above), and that you can still achieve the same thing by using the delete-client
method, we thought that a severity of Low
is more appropriate.
--
The goal of the application is to speed up the work of insurance agents, however a lot of the commands are one-by-one, like for example I cannot mass delete some set of users. Maybe range-based commands (e.g delete 1-20) would help speed up the app to make it more usable for insurance agents as efficiency / productivity is a major pain point for this target group so it is of critical importance
[original: nus-cs2103-AY2425S1/pe-interim#670] [original labels: severity.Medium type.FeatureFlaw]