My tester seems to have reported a feature flaw as a documentation bug, during the the documentation phase. Does that serve as grounds for rejection? The tester reported the bug during the documentation stage, where he seems to have changed the type so that it becomes "valid" during the documentation stage.
@RunjiaChen
If you think the the correct bug type is FeatureFlaw, and not DocumentationBug, you can change the type first. After that, you make the accept/reject decision based on that correct type.
In Catcher, it is stated:
However, on the website, is is also stated:
My tester seems to have reported a feature flaw as a documentation bug, during the the documentation phase. Does that serve as grounds for rejection? The tester reported the bug during the documentation stage, where he seems to have changed the type so that it becomes "valid" during the documentation stage.