search

Whysochong / pe

0 stars 0 forks source link

UI doenst show which project staff is attached to #15

Open Whysochong opened 1 year ago

Whysochong commented 1 year ago

image.png

This is a huge problem when trying to use delstaff function as user may not remember which project the staff belongs to and will not be able to provide it

nus-pe-bot commented 1 year ago

Team's Response

The delstaff command is meant to work from the given starting point of a project - the purpose of this command is so that a user can delete staff from a specific project, and so the argument that a user may not remember what project a staff member is from is invalid, as the user should not be beginning from a standpoint of what staff member to delete from an unknown place, but rather what project they want to remove a staff from. Moreover, we have advised users to first use the view command before any staff commands in our user guide.

image.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: I disagree with your reasoning. Imagine a very busy SME is using this application and they have way too many projects going on. How would they know which staff are working on which projects?

You stated that the user should not be beginning from a standpoint of what staff member to delete from an unknown place but I beg to differ. What if it's an inactive staff or a staff they fired for other reasons (other than work performance) or a worker that just quit? The management might not know which project this staff was working on and it would be a problem trying to find which project the staff previously worked on, so as to delete him. Furthermore, they might have a lot of stuff too, and a lot of contracted staff that they may not know well.

Or alternatively, you can have a compiled list of all the workers with the projects they are working on displayed as one of their fields and it would be a lot clearer.

:question: Issue severity

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

Reason for disagreement: image.png

Please refer to this.

I think medium severity is a little too harsh. Verylow is just for comestic and UI issues but this extends beyond that. There's a logic gap that was failed to address. But this deserves at least a low severity. The situation that I just describes above happens rarely and doesn't affect day-to-day operation until a worker quit or leave his job.