Bug 1749953 - Service Requests Requester dropdown not sorted
Summary: Service Requests Requester dropdown not sorted
Keywords:
Status: POST
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.10.8
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.12.0
Assignee: Zita Nemeckova
QA Contact: Niyaz Akhtar Ansari
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks: 1753691 1767660
TreeView+ depends on / blocked
 
Reported: 2019-09-06 21:10 UTC by Ryan Spagnola
Modified: 2020-04-05 03:16 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1753691 1767660 (view as bug list)
Environment:
Last Closed:
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)

Description Ryan Spagnola 2019-09-06 21:10:36 UTC
Description of problem:
The requester dropdown from Services -> Requests page is no longer sorted alphabetically

Version-Release number of selected component (if applicable):
5.10.8

How reproducible:
Always

Steps to Reproduce:
1. go to Services -> Requests
2. click on the Requester dropdown
3.

Actual results:
not sorted alphabetically like in previous versions

Expected results:
organized sorting (alphabetically)

Additional info:
Causing issues when trying to troubleshoot specific requests for a specific user

Comment 6 CFME Bot 2019-09-18 12:16:20 UTC
New commit detected on ManageIQ/manageiq-ui-classic/master:

https://github.com/ManageIQ/manageiq-ui-classic/commit/7bc1db07b6d79e4413a06d44864a0ea62cfdf3ed
commit 7bc1db07b6d79e4413a06d44864a0ea62cfdf3ed
Author:     Zita Nemeckova <znemecko@redhat.com>
AuthorDate: Wed Sep 18 04:54:58 2019 -0400
Commit:     Zita Nemeckova <znemecko@redhat.com>
CommitDate: Wed Sep 18 04:54:58 2019 -0400

    Sort Requester dropdown by label

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1749953

 app/controllers/miq_request_controller.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


Note You need to log in before you can comment on or make changes to this bug.