Allowing assignee = QA kinda defeats the purpose. We should prevent this happening.
Priority: -- → P3
Target Milestone: --- → Future
Moving to new Bugzilla product ...
Assignee: justdave → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → 2.13
Well, allowing assignee = QA is a very useful feature for testing things without spamming someone else. Ok, you can always create new accounts, but it can be kind of inconvenient if you have only very few different email addresses. Also, in my bugzilla installation there are some areas where I'm really both default QA contact and default assignee, and I think mozilla.org has the same setup for some components.
If you're both I suggest you want to leave one blank as there's no point having verification without it being a separate person. We could certainly allow an admin to disable this, or make it a SHOULD option (so it gives a warning but allows it with confirmation). The important thing here is people don't forget to reassign the QA to someone different if the QA becomes the assignee.
How would you handle an upgrade where the database could already have certain bugs where the owner and the QA contact are the same?
This would do nothing to fix the problem unless you specified something to do (eg blank QA). See bug #96635. Like other problems hanging off that bug, I would expect some sort of whining about the problem.
Target Milestone: Future → ---
When the QA decides to fix a bug himself, he will reassign the bug to him. I see nothing wrong with that. And I don't think it worths implementing additional code for that.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.