| Summary: | Can't watch a component | ||
|---|---|---|---|
| Product: | [Infrastructure] Bugzilla | Reporter: | Darren Hart <dvhart> |
| Component: | bugzilla | Assignee: | Yongkang You <yongkang.you> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | infras.bug.watcher, Infras.watcher, sgw |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Darren Hart
2011-03-11 12:04:29 UTC
Hart, Please watch this user: yp.kernel.watcher@fake.user It is for all kernel bugs. We don't want to set component watcher one by one for users, as it brings too much overhead (add/remove) to Bugzilla Admin. User should choose the right fake user to watch. Interesting, is there a list of fake.user ids anywhere? As to admin overhead - watching components was just part of the tool that users could check and uncheck as part of their email preferences in this other instance of bz that I used. I didn't think it required any admin interaction at all. It exposed a much more intuitive interface. For now, I'll watch this fake.user, but the solution isn't self-discoverable, and that will lead to more and more admin overhead answering similar questions as our user base grows. I think we should consider looking at augmenting our bz implementation to expose this subscription to components feature to users, rather than relying on the fake.user hack. Darren, We have a wiki to introduce all watch user list. https://wiki.yoctoproject.org/wiki/Watch_Yocto_Bugs User could select either fake user to watch. |