Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev response phase queries #98

Open
aquohn opened this issue Nov 17, 2019 · 1 comment
Open

Dev response phase queries #98

aquohn opened this issue Nov 17, 2019 · 1 comment
Labels

Comments

@aquohn
Copy link

aquohn commented Nov 17, 2019

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.

@okkhoy
Copy link
Collaborator

okkhoy commented Nov 17, 2019

Hmmm, this is a bit tricky.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants