Description of problem: Trying to add a new category very similar to an existing category name. It will not allow the same display name, but gives the error that the description. not display name has already been used.
Libor, Let's cleanup labels on "MIQ Categories" tab & "MIQ Tags" screens. 1. Change label on MIQ Categories from "Display Name" to "Description" on both list screen and edit screen. Change label "Description" to "Long Description" on edit screen. 2. Change label on MIQ Tags screen "Description" to "Long Description" 3. Change flash message on follwouing 2 lines to match labels on MIQ Categories edit screen: https://github.com/lpichler/manageiq/blob/master/app/controllers/ops_controller/settings/tags.rb#L56 & https://github.com/lpichler/manageiq/blob/master/app/controllers/ops_controller/settings/tags.rb#L59 Let me know if you have any questions. Thanks, ~Harpreet
https://github.com/ManageIQ/manageiq/pull/4921
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/a0da33fd501dbc312683aa6fdfed76170a9c12b2 commit a0da33fd501dbc312683aa6fdfed76170a9c12b2 Author: Libor Pichler <lpichler> AuthorDate: Fri Oct 16 11:27:03 2015 +0200 Commit: Libor Pichler <lpichler> CommitDate: Mon Oct 19 10:55:53 2015 +0200 Change "Display" label in "MIQ Categories" & "MIQ Tags" screens https://bugzilla.redhat.com/show_bug.cgi?id=1265393 Label "Description" changed as well app/controllers/ops_controller/settings/tags.rb | 4 ++-- app/views/ops/_category_form.html.haml | 8 ++++---- app/views/ops/_classification_entries.html.haml | 2 +- app/views/ops/_settings_co_categories_tab.html.haml | 2 +- app/views/ops/_settings_co_tags_tab.html.haml | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-)
https://github.com/ManageIQ/manageiq/pull/4958
https://github.com/ManageIQ/manageiq/pull/4853
The UI is changed according to the Comment 4 in 5.5.0.7.
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/RHSA-2015:2551