Description of problem: ----------------------- The Tags are not sorted while tagging services in SUI. See attached screen shot. Version-Release number of selected component (if applicable): ------------------------------------------------------------- 5.8.0.4 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1.Tag a service in SUI by clicking 'Policy' and then clicking 'Edit Tags'. Actual results: --------------- Tags not sorted while tagging services in SUI Expected results: ---------------- Tags should be sorted while tagging services in SUI, just like they are sorted in admin UI Additional info: ----------------
Created attachment 1264858 [details] Screen shot of Edit Tag dropdown for Services in SUI
https://github.com/ManageIQ/manageiq-ui-service/pull/602
New commit detected on ManageIQ/manageiq-ui-service/master: https://github.com/ManageIQ/manageiq-ui-self_service/commit/1dd4af4e320ec5d5f24aecd52ad097c33d37f061 commit 1dd4af4e320ec5d5f24aecd52ad097c33d37f061 Author: Josh Langholtz <jjlangholtz> AuthorDate: Wed Mar 22 14:38:26 2017 -0400 Commit: Josh Langholtz <jjlangholtz> CommitDate: Wed Mar 22 15:26:56 2017 -0400 Sort tagging widget tag categories * Add tags back to `getServices` request attributes for bulk taggging * Increase width enough to fully display initial category and value * Update specs to account for sorted categories https://www.pivotaltracker.com/story/show/142251411 https://bugzilla.redhat.com/show_bug.cgi?id=1434174 client/app/services/services-state.service.js | 1 + client/app/shared/tagging/_tagging.sass | 4 ++-- client/app/shared/tagging/tagging.component.js | 4 ++-- client/app/shared/tagging/tagging.component.spec.js | 11 +++++------ 4 files changed, 10 insertions(+), 10 deletions(-)
Verified in 5.8.0.8
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-2017:1367