Created attachment 1072066 [details] CFME 5.3 did have a description text Description of problem: CFME 5.3 did have a description text next to the export button: "Export all Datastore classes and instances to a file" This text is missing in 5.4 making it a bit more difficult to understand the purpose of the button. Version-Release number of selected component (if applicable): cfme-5,4 How reproducible: always Steps to Reproduce: 1. Navigate to "Automate, Export/Import" Actual results: no description text Expected results: some basic explanation about the function of the export button Additional info: I attached screenshots of CFME 5.3 and 5.4 to see the difference.
Created attachment 1072067 [details] CFME 5.4 does not have a descriiption of the Export button
Erik - Not sure when this got lost but can you take a quick look and try to restore this text.
https://github.com/ManageIQ/manageiq/pull/5459
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/f2576f19b94f06cbd8e3b05494f961ec0b47c8df commit f2576f19b94f06cbd8e3b05494f961ec0b47c8df Author: Erik Clarizio <eclarizi> AuthorDate: Mon Nov 16 08:28:41 2015 -0800 Commit: Erik Clarizio <eclarizi> CommitDate: Mon Nov 16 08:28:41 2015 -0800 Add description about datastore export https://bugzilla.redhat.com/show_bug.cgi?id=1261833 app/views/miq_ae_tools/_import_export.html.haml | 2 ++ 1 file changed, 2 insertions(+)
New commit detected on cloudforms/cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=d0589a54bf3feaf48e3bce932d0bd2d8ae65f0de commit d0589a54bf3feaf48e3bce932d0bd2d8ae65f0de Author: Erik Clarizio <eclarizi> AuthorDate: Mon Nov 16 08:28:41 2015 -0800 Commit: Erik Clarizio <eclarizi> CommitDate: Tue Dec 8 08:39:12 2015 -0800 Add description about datastore export https://bugzilla.redhat.com/show_bug.cgi?id=1261833 app/views/miq_ae_tools/_import_export.html.haml | 2 ++ 1 file changed, 2 insertions(+)
Verified fixed in 5.6.0.1-beta2.20160413141124_e25ac0e.
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/RHBA-2016:1348