shuyangk / pe

0 stars 0 forks source link

Having only one panel might cause inconvenience to users. #11

Open shuyangk opened 11 months ago

shuyangk commented 11 months ago

The application only has one panel that displays information at any point in time, while having multiple different data types. It could be inconvenient for a user that is trying to map courses to constantly toggle between the local courses and partner courses to find the course they want, and they could forget the partner course eventually. Perhaps having multiple panels would improve usability.

image.png

soc-pe-bot commented 11 months ago

Team's Response

No details provided by team.

The 'Original' Bug

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

Hard to map courses due to UI limitation

Due to the limitation of the UI, I think it is quite challenging for the user to have an overview of the both the partner course list and local course list. I thought this was a problem as mapping of the courses would take longer since the user can only view either the partner course or local course list at once.


[original: nus-cs2103-AY2324S1/pe-interim#3681] [original labels: severity.Low type.FeatureFlaw]

Their Response to the 'Original' Bug

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

Users are already able to search/sort by local course attributes and partner course attributes. For instance, search for mappings for CS3230. Or sort by partner course name. \ Users are don't need to look at the local course / partner course list when managing mappings, as they should be familiar with courses they're mapping.

Items for the Tester to Verify

:question: Issue duplicate status

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

Reason for disagreement: [replace this with your explanation]


## :question: Issue response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** I believe instead of rejecting it, it could potentially be classified as Not in Scope, as this hinders usability of the application, and can definitely be worked on in a future iteration.