Bug 1003910
Summary: | Needinfo adds the target user to the CC list | ||
---|---|---|---|
Product: | [Community] Bugzilla | Reporter: | Radek Bíba <rbiba> |
Component: | Creating/Changing Bugs | Assignee: | PnT DevOps Devs <hss-ied-bugs> |
Status: | CLOSED NOTABUG | QA Contact: | tools-bugs <tools-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4 | CC: | rjoost |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-04 01:11:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Radek Bíba
2013-09-03 13:44:40 UTC
Been set as the requestee on a flag will CC: that user on the bug if they have the "Automatically add me to the CC list of bugs I am requested to review" turned on. This is on by default in upstream Bugzilla and Red Hat Bugzilla. It makes no difference what relationship you or the requestee user currently have to the bug. If a user has an issue with this, their best course of action would be to change this preference in their settings. (FWIW, I have this option disabled in my preferences) -- simon Well, then it's a strange new feature with questionable default settings. Shouldn't BZ ask me if I want to CC the user at the same time? Or, shouldn't it consider the reporter (and QA contact) a special case? (In reply to Radek Bíba from comment #2) > Shouldn't BZ ask me if I want to CC the user at the same time? No, it definitely should be up to the user (the requestee) to decide if they want to be CC:ed on the bug, not the person making the change (the requester). > Or, shouldn't > it consider the reporter (and QA contact) a special case? No, it shouldn't, for the reason stated above. -- simon |