Open ZhangAnli opened 3 years ago
This is a purely cosmetic Feature flaw
instead.
Team chose [type.FeatureFlaw
]
Originally [type.FunctionalityBug
]
Reason for disagreement: This is not a feature flaw, but rather a functionality bug as the help function is not working as intended due to the typo. A flaw would suggest the feature is not complete, but in this case the help function is complete but erroneous. It would be more correct to say that the help command is not really helping the user (punny!) and is not working as intended which by definition is a functionality bug.
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: severity.VeryLow as stated is for purely cosmetic flaws. However, in this instance, the example given is a sample EXAMPLE command from the help display, not just any sentence error for example in a UG. The fact that this error occured in the help display (that should be helping the user) should be the deciding factor on why this isn't a simple cosmetic flaw. This should be given at least a severity.Low as it did cause me minor inconvenience when trying to understand how to input their status clean command and slowed down testing for me.
No details provided.
Steps: help (scroll to status)
The example provided in the help command box should have been status clean, instead of statusclean, small typo error.