You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we do not accept bugs (or tag multiple bugs as duplicates and do not accept the original), do we need to downgrade the severity of the issue (and its duplicates, if any)? Or leave it as is? Assigning a severity may not make sense for e.g. correct behaviour or unclear behaviour. But for "Cannot Reproduce" bugs, I suppose it might.
The text was updated successfully, but these errors were encountered:
If it is a rejected bug and the tester/teaching team thinks it is a valid rejection (based on your explanation) changing the severity or not doing anything doesn't matter as it is a rejected bug.
However, if you gave a reason that is not good enough to convince the tester/teaching team, it may help to assign the correct severity even when you reject the bug.
If there are duplicates, retain one bug as original and do any changes to this one. No need to bother about the duplicates.
If we do not accept bugs (or tag multiple bugs as duplicates and do not accept the original), do we need to downgrade the severity of the issue (and its duplicates, if any)? Or leave it as is? Assigning a severity may not make sense for e.g. correct behaviour or unclear behaviour. But for "Cannot Reproduce" bugs, I suppose it might.
The text was updated successfully, but these errors were encountered: