Closed Bug 96333 Opened 25 years ago Closed 19 years ago

Pref to e-mail QA Contact when a user attempts to change a bug he is unauthorized to change/view

Categories

(Bugzilla :: Email Notifications, enhancement)

Product:
Bugzilla
Component:
Email Notifications
Version:
2.13
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: caillon, Unassigned)

Details

Timeless's idea. How did I get stuck filing this one? :P This is most useful when someone tries to dupe to a bug they can't see. Possibly they know the bug # but just can't see it. Also useful on smaller projects when not many users can confirm or edit bugs, but you want to know when someone tries so you can make the changes yourself. Something like that.
Moving to new product Bugzilla...
Assignee: justdave → jake
Component: Bugzilla → Email
Product: Webtools → Bugzilla
Target Milestone: --- → Bugzilla 2.16
Version: Bugzilla 2.13 → 2.13
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Changing default owner of Email Notifications component to JayPee, a.k.a. J. Paul Reed (preed@sigkill.com). Jake will be offline for a few months.
Assignee: jake → preed
Summary: [RFE] Pref to e-mail QA Contact when a user attempts to change a bug he is unauthorized to change/view → Pref to e-mail QA Contact when a user attempts to change a bug he is unauthorized to change/view
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Assignee: preed → email-notifications
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
I can't ever see us actually doing this, and I've never seen a real-world situation where it would be really useful.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.