Red Hat Bugzilla – Bug 1186932
Config Groups: Tooltips used for adding/removing classes to a config group could be streamlined
Last modified: 2016-07-27 04:46:54 EDT
Description of problem: When you create or edit a config group, the tooltip for adding a class is "Click to add <class name>". After you click that, you can then remove it, and our tooltip for that is "Click to undo adding this class". We could make those more concise if we simply said "Add this class" and "Remove this class". By nature of being a tooltip on a clickable element, I think it's implied that if they click it, the action the tooltip says will happen. 'Remove' is the more expected opposite to 'add' than 'undo adding'. Version-Release number of selected component (if applicable): 6.0.6
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created attachment 985382 [details] Click to undo adding this class
Created redmine issue http://projects.theforeman.org/issues/9453 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/9453 has been closed ------------- Anonymous Applied in changeset commit:f9d9ece7f135fc583b8df138a305267abd289a23.
VERIFIED: # rpm -qa | grep foreman foreman-gce-1.11.0-0.develop.201511062002gitd3c978e.el7.noarch hp-bl465cg7-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-bl465cg7-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch foreman-release-1.11.0-0.develop.201511062002gitd3c978e.el7.noarch foreman-ovirt-1.11.0-0.develop.201511062002gitd3c978e.el7.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch foreman-libvirt-1.11.0-0.develop.201511062002gitd3c978e.el7.noarch foreman-postgresql-1.11.0-0.develop.201511062002gitd3c978e.el7.noarch foreman-1.11.0-0.develop.201511062002gitd3c978e.el7.noarch tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch hp-bl465cg7-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch tfm-rubygem-foreman_discovery-4.1.2-1.fm1_11.el7.noarch foreman-compute-1.11.0-0.develop.201511062002gitd3c978e.el7.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch foreman-debug-1.11.0-0.develop.201511062002gitd3c978e.el7.noarch foreman-proxy-1.11.0-0.develop.201511020918git26aba85.el7.noarch foreman-vmware-1.11.0-0.develop.201511062002gitd3c978e.el7.noarch tfm-rubygem-hammer_cli_foreman-0.4.0-1.201510201150gitab068d9.el7.noarch tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch foreman-release-scl-1-1.el7.x86_64 tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch steps: When you create or edit a config group, the tooltip for adding a class is "Click to add <class name>". After you click that, you can then remove it, and our tooltip for that is "Click to remove <class name>"
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:1500