Open
Bug 715101
Opened 14 years ago
Updated 9 years ago
The assignee and QA contact are not updated when the reporter changes the component and the reporter doesn't have editbugs privileges
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Tracking
()
NEW
People
(Reporter: Swarnava, Unassigned)
References
Details
User Agent: Opera/9.80 (J2ME/MIDP; Opera Mini/4.2.22537/26.1305; U; en) Presto/2.8.119 Version/10.54
Steps to reproduce:
If i create a bug and set the component wrong, if i change the component, the qa contact not change,is there need permission to change qa contact ?
Example:-https://bugzilla.mozilla.org/show_bug.cgi?id=715087
no special permissions are required.
by default the qa contact is updated to match the new component, however if you untick 'Reset QA Contact to default', this won't happen. i suspect that's what happened in your case.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 2•14 years ago
|
||
Where is the option to untick? I didnt uncheck anything manually
ah, sorry; this is indeed a problem relating to users without editbugs.
Assignee: general → create-and-change
Status: RESOLVED → REOPENED
Component: Bugzilla-General → Creating/Changing Bugs
Ever confirmed: true
Resolution: WORKSFORME → ---
Summary: QA contact not change after changing component → QA contact is not updated when changing the component if the user doesn't have editbugs
Version: 4.3 → 4.0.3
Comment 4•14 years ago
|
||
This is only an issue if the reporter tries to change the component and he doesn't have editbugs privs. I would have to check, but maybe this behavior is intentional.
Severity: normal → minor
Status: REOPENED → NEW
Summary: QA contact is not updated when changing the component if the user doesn't have editbugs → The assignee and QA contact are not updated when the reporter changes the component and the reporter doesn't have editbugs privileges
We've had one of our developers notice this behaviour.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370075
Intentional or not, this will lead to bugs that aren't noticed by the new owners. I'm wondering if this is a regression...
Comment 6•13 years ago
|
||
Ping. This bug makes Bugzilla mails unreliable.
Since it can lead to "data loss" in the real world, it should not be "minor".
Comment 7•12 years ago
|
||
(In reply to Denis Roy from comment #5)
> Intentional or not, this will lead to bugs that aren't noticed by the new
> owners. I'm wondering if this is a regression...
It's not a regression. Till Bugzilla 2.18, everyone was free to reassign bugs as they wished, meaning that they could reassign bugs to themselves and get privileges (because the assignee and QA contact have extra privileges). But since Bugzilla 2.20, we enforced the policy to have editbugs privileges to be allowed to edit the assignee and QA contact, see bug 266579.
We are in a grey area here. Probably it's fine to reassign the bug to the *default* assignee and QA contact only when the product and/or component changes. And for consistency with users with editbugs privileges, a checkbox should let you reassign them or not (to not override the current assignee and QA contact if that's not required).
Keywords: qawanted
Comment 8•11 years ago
|
||
> We are in a grey area here. Probably it's fine to reassign the bug to the
> *default* assignee and QA contact only when the product and/or component
> changes. And for consistency with users with editbugs privileges, a checkbox
> should let you reassign them or not (to not override the current assignee
> and QA contact if that's not required).
Yes, that's what I'd expect. And the "Reset Assignee/QA Contact to default" checkboxes should be checked by default, just like when an editbugs user touches product/component fields.
You need to log in
before you can comment on or make changes to this bug.
Description
•