Bug 1404162 - Please change the text for oVirt Team custom field.
Summary: Please change the text for oVirt Team custom field.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: 4.4
Assignee: Matt Tyson 🤬
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 09:02 UTC by Yaniv Lavi
Modified: 2018-12-09 06:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-30 01:00:39 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Yaniv Lavi 2016-12-13 09:02:34 UTC 
Description of problem:
DWH team has changed to metrics and help should be updated to reflect this.
The new text replacing DWH should be:
"""
- Metrics:
  + Data warehouse (DWH) issues.
  + Metrics store issues.
  + Alerting framework issues.
  + Metrics visualizations issues.
"""
Comment 1 Yaniv Lavi 2016-12-13 09:03:13 UTC 
Bugzilla request asked me to assign this to you.
Comment 2 Rony Gong 🔥 2016-12-19 09:06:34 UTC 
Tested on QA environment(5.0.3-rh19)
Result: Pass
Steps:
1. Go to
https://bz-web.host.qe.eng.pek2.redhat.com/page.cgi?id=fields.html#cf_ovirt_team
2. Check it show as:
...
Reports - Reports engine issues.
Metrics:
Data warehouse (DWH) issues.
Metrics store issues.
Alerting framework issues.
Metrics visualizations issues.
SLA:
Comment 3 Rony Gong 🔥 2017-01-09 09:56:18 UTC 
Tested on QA environment(4.4.12065-1.el6)
Result: Pass
Steps:
1. Go to
https://bzweb.host.qe.eng.pek2.redhat.com/page.cgi?id=fields.html#cf_ovirt_team
2. Check it show as:
...
Reports - Reports engine issues.
Metrics:
Data warehouse (DWH) issues.
Metrics store issues.
Alerting framework issues.
Metrics visualizations issues.
SLA:
Comment 4 Matt Tyson 🤬 2017-01-30 01:00:39 UTC 
This change is now live. If there are any issues, do not reopen this bug.                                                                                                           
Instead, you should create a new bug and reference this bug.
Note You need to log in before you can comment on or make changes to this bug.