nus-pe-script
commented
9 months ago Team's Response
We reject this FunctionalityBug. We contest that it doesn't affect correctness or usability. It is an intended feature left in for those who might want to reorder their columns to gain an alternate view of the matrix. The shifting of the columns occurs only when clicking and dragging, whereas scrolling doesn't require any of those actions. Even then, the change is reversible and is left in the UI to make it more flexible for users who prefer alternative views.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I disagree with the rejection of this bug.
The shifting of the columns occurs only when clicking and dragging, whereas scrolling doesn't require any of those actions.
I am specifically referring to the scrolling of the task in the table cells - which does not listen for the scroll wheel event. Notice the horizontal scroll here.
You can see the task gets cut off if it is a bit too long. I believe that scrolling the individual cells on this table is an important part of the application workflow - this table is meant to help me check which items are of higher priority at a glance, so if I had tasks that are long, I may need to scroll to differentiate what task I am to prioritize.
As an example, a task named Prepare Notes for XYZ Meeting and Prepare Notes for ABC Meeting could be cut off by the table cells and require me to scroll to check which meeting its referring to.
Certainly, this can be reordered to gain an alternate view of the matrix, and I can see the merit in that. However, I argue that the response to this should have been response.NotInScope and bugtype.FeatureFlaw rather than an outright rejection, as currently it is too easy to accidentally displace columns when you don't mean to do it due to the workflow I had specified above.
When attempting to scroll the individual cells inside the list to read more information on the task, I had been able to reorder the columns of the list.
Users will need to scroll tasks to read them occasionally, and it is more likely to occur at the top where highest priority tasks are located, which was why this was listed as a Medium Severity Bug.