sorting and filtering cannot be done by CLI

[wpx12011]

The tp constraint says that the product should target user who prefer typing, so it contradicts this requirement when these 2 functions has no command but only GUI interaction.

[nus-pe-script]

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Some features only available though clicking instead of CLI based commands

Reasoning

The sorting and filtering features are only available through clicking, but Duke Driver is targetted towards users who prefer typing to mouse interactions.

Severity level is low because the features are still perfectly usable, but it does not fit the target audience (who prefers typing).

---

_{[original: nus-cs2103-AY2223S2/pe-interim#393] [original labels: severity.Low type.FeatureFlaw]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

No details provided by team.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue severity

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

• I disagree

Reason for disagreement:

I disagree the team's reclassification of severity level. As the label explanation suggests, severity.Medium suggests that the bug causes occasional inconvenience, but the application is usable with it. Therefore, the team's reasoning of "Severity level is low because the features are still perfectly usable" does not hold, since severity.Medium also suggests the application is usable.

Furthermore, the team suggests " but it does not fit the target audience (who prefers typing)" in their own reasoning. This shows that they are aware that their product is not targeting their own audience. A feature that is designed not to match the target audience is an important feature flaw.

---