Bug 1419544

Summary: forms don't contain '?' with link to help
Product: Red Hat Enterprise Virtualization Manager Reporter: Lucie Leistnerova <lleistne>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED ERRATA QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bgraveno, gshereme, lsurette, pstehlik, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.1.1Keywords: Reopened, TestOnly
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-17 16:27:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
form_header none

Description Lucie Leistnerova 2017-02-06 13:18:25 UTC
Created attachment 1248032 [details]
form_header

Description of problem:
There is no link to help '?' in form headers in admin portal. For example see attachment.

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-4.1.0.4-0.1.el7.noarch

Comment 1 Greg Sheremeta 2017-02-06 13:45:58 UTC
This is expected for 4.1 beta, because there is no documentation ready yet. It will be there closer to GA. Closing. Thanks for noticing!

Comment 2 Pavel Stehlik 2017-02-06 14:13:33 UTC
Can we keep it open please? I hope there is no problem with that. We can retarget to GA easily. 
Once close to GA - QE will check and this issue won't go out of radar, thank you.
P.

Comment 3 Greg Sheremeta 2017-02-06 14:14:28 UTC
Of course :)

Comment 4 Lucie Leistnerova 2017-04-03 07:43:54 UTC
in version ovirt-engine-4.1.1.7-0.1.el7.noarch '?' are back

Comment 7 errata-xmlrpc 2017-07-17 16:27:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:0997