So for one of my bug reports I suggested an improvement that would make a feature more useful than can be and placed it under FeatureFlaw. The team's response was that they actually had created a command that included this improvement already but they pretty much forgot to document it down in their UG or Help Window and that the bug type should be DocumentationBug. I am unsure whether to accept or challenge this type change as on the one hand it could be a DocumentationBug under the category of Undocumented Features, but on the other hand, I feel like I am unjustly losing marks for accuracy as there was actually no way for me to know that they actually already had this feature improvement somewhere hidden in their app unless I was to stumble across it accidentally.
@nws321 As we are more relaxed about the bug type this semester, I'll update our grading scheme to ignore the type.* when calculating the accuracy bonus. So, this should not matter.
So for one of my bug reports I suggested an improvement that would make a feature more useful than can be and placed it under
FeatureFlaw
. The team's response was that they actually had created a command that included this improvement already but they pretty much forgot to document it down in their UG or Help Window and that the bug type should beDocumentationBug
. I am unsure whether to accept or challenge this type change as on the one hand it could be aDocumentationBug
under the category of Undocumented Features, but on the other hand, I feel like I am unjustly losing marks for accuracy as there was actually no way for me to know that they actually already had this feature improvement somewhere hidden in their app unless I was to stumble across it accidentally.