Open yhtMinceraft1010X opened 3 years ago
In terms of grading, yes. In terms of bug triaging, they are different. For example, what it communicates to the tester ('this bug report is invalid' vs 'this is valid, but not important enough to do just yet') and in terms of how you'll act on them in future (if you were to continue this project). NotInScope
issues can be reconsidered in future versions while Rejected
will be discarded right-away.
So, although it doesn't matter for grading, it is still good to choose the more appropriate response so that there is some learning value as well.
I'm not sure exactly why we have both since there's no penalty for the developer in both cases. Wouldn't saying that a bug is not in scope be akin to rejecting it for grading purposes?