search

minreiseah / pe

0 stars 0 forks source link

Assigning tasks is cumbersome when there are many tasks/employees #8

Open minreiseah opened 5 months ago

minreiseah commented 5 months ago

As the user is required to know the employee IDs before keying in the command: assigntask [task-id] [employee-id], this process is quite painful to handle. The current workflow is difficult to process. I have to:

  1. list employees
  2. keep multiple employee ids in my head/write it down
  3. list the tasks
  4. key in assigntask [task-id] [employee-id] (multiple times) to assign the task to potentially many employees.

The issue here is in point (2) where the user has to remember the employee ids. In a larger corporation with tens or hundreds of IDs, this would hamper accessibility.

nus-se-bot commented 5 months ago

Team's Response

I believe the main issue here is that listing the tasks removes the list of employees away from the screen hence users have to memorize ids. Issue #3482 tackles this problem.

The 'Original' Bug

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

Unable to see list of tasks alongside list of employees

It may be more convenient for users to be able to see both the list of tasks and list of employees beside each other, so that the user can easily decide which tasks to assign to which employees, which would help with meeting the needs of the user better.

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

Their Response to the 'Original' Bug

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

Valid point, but it has been addressed in planned enhancements point 2.

Since it has been addressed in planned enhancements we will reject this issue.

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: The "duplicate issue" suggests splitting their screen to provide two views. My issue concerns the confusing and convoluted workflow of assigning a task in their application. My issue makes no suggestions as to the UI. This is not a duplicate issue.

## :question: Issue response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** I don't see why this was outright rejected as it does not pertain to enhancement #2 (splitting the UI) in the developer guide at all. My issue concerns the confusing workflow, which the team did not address.