liauzhanyi / pe

0 stars 0 forks source link

confusing constraints #9

Open liauzhanyi opened 1 week ago

liauzhanyi commented 1 week ago

Screenshot 2024-11-15 at 5.25.03 PM.png

job code and tags and not related but some times I can match partially some times I cannot, as a user it is a hard to memorise specific interactions instead of features format.

soc-pe-bot commented 1 week ago

Team's Response

Thank you for raising this issue. We felt that this is of a lower priority than what we have done in v1.6.

We understand that the specific instructions might be hard to memorise. However, we believe that only a small number of people will be affected by this. From the point of view of the user, if they want to MassReject applicants by job code and tag, they most likely already have a specific job code and tag in mind. Hence, they don't even need to memorise specific interactions and can proceed with the job code and tag that they already have in mind.

Hence, our app is still usable and implementing this enhancement could be postponed to the further iterations

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your explanation]


## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** I agree with what you mentioned "From the point of view of the user, if they want to MassReject applicants by job code and tag, they most likely already have a specific job code and tag in mind." However, it is not the issue of whether they have the (full) job code in mind, but rather the user expected usage and habits. to illustrate, consider the I as the user uses `massreject j/swe- t/n` all new applicants for swe related jobs and similar commands for others jobs. Then, knowing the existent of the feature to use mass reject all stages of swe job applicants the I tries `massreject j/swe-` expecting to work only to receive an error message and having to retype the full job code. Given the definition of severity, ![Screenshot 2024-11-19 at 2.43.22 PM.png](https://raw.githubusercontent.com/liauzhanyi/pe/main/files/58bca191-817c-4430-be42-7b5b25767e09.png) While I agree that this is definitely not a major problem, I disagree that only a small number of people will be affected by this as I believe the scenario I mentioned above is a very common user expectation and behaviour. In fact, I would even argue that **most** user will meet the error at least once and has to re-adjust their command until they memorise the structure based on muscle memory. Hence, based on the number of users affected, I believe it constitutes a `severity.Medium`