jerrrren / pe

0 stars 0 forks source link

The format provided in Error message in duration does not match UG #3

Open jerrrren opened 1 year ago

jerrrren commented 1 year ago

Screenshot (89).png As seen in the UG, the numerical input for duration is represent by DURATION, while the alphabetical input is represented as a UNIT, however in the error message the format is given as {number OR decimal} {duration} which will cause confusion. Screenshot (90).png

soc-pe-bot commented 1 year ago

Team's Response

We concede that this is a typo on our part. The "duration" in the error message should instead be "unit". Hence for typos, the severity should be very low.

Items for the Tester to Verify

:question: Issue severity

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

Reason for disagreement: I disagree that this should be severity very low as it is not simply a typo of a few alphabets. Additionally, in the docs, Duration came first but in the error message Duration came last. The fact that the same words is used in two different context, in the UG to refer to the integer input and in the error message to refer to the alphabetical unit can cause confusion to some users and hence does cause inconvenience. Considering the main issue is the use of the same word to incorrectly refer to another parameter in the same command, I would argue that the severity should at least be low as it does affect the usage of the application.