Bug 729334
Summary: | [Beaker] RFE system page POC field | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Jeff Burke <jburke> |
Component: | web UI | Assignee: | Raymond Mancy <rmancy> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 0.6 | CC: | bpeck, dcallagh, ebaak, mcsontos, mishin, pbunyan, peterm, rmancy, stl, tburke |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | MC | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-11-07 07:22:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeff Burke
2011-08-09 14:59:48 UTC
The Toggle Search should also allow this field for searching What would be the difference between "point of contact" and owner? Dan, We have systems in Beaker that are owned by the kernel group but are supported by a specific admin in engineering operations known as POC. Since some of these systems are unique and for development only. We would like to insure that associates know who to contact if they need any thing done with that system. The owner of these systems is ambiguous when set to admin and some admins may not know anything about the specific hardware configurations. We have an arrangement with engineering operations that we have a dedicated resource know as POC aka Notify CC. But since the Notify CC has been hidden I am requesting a new field that is not hidden Regards, Jeff Could we just change the owner of these systems from "admin" to the specific admin who is responsible? I'm concerned that this RFE would leave us with three different system fields (owner, notify cc, POC) with largely overlapping meanings. This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration. Please feel free to reopen the bug with additional information and/or business cases behind it. |