Bug 1481840
| Summary: | Services Requests not showing all requests from 30 days | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Jeffrey Cutter <jcutter> |
| Component: | UI - OPS | Assignee: | Robin Knaur <rknaur> |
| Status: | CLOSED ERRATA | QA Contact: | Shveta <sshveta> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.8.0 | CC: | hkataria, jhardy, mpovolny, obarenbo, rknaur, simaishi, sshveta |
| Target Milestone: | GA | ||
| Target Release: | 5.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.10.0.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-02-07 23:02:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Jeffrey Cutter
2017-08-15 20:42:44 UTC
Created attachment 1313841 [details]
Filter by settings and sorted by request id shows that data goes back 30 days
Created attachment 1313842 [details]
Now inverse sorted by request id and shows that the results at the bottom do not go back 30 days
I am sorry, but I can't reproduce this issue, it seems to me, that all request 30 days back are shown, regardless of sorting. Hi Robin, How many requests do you have in your history over the last 30 days? I think you will need more than a screens worth to be impacted, say more than 30. Thanks, -Jeff Hey Jeff, I have created more requests and I found the bug. Sorting order changes when you go to next page in the table. When you set descending order on first page, on the second page are request sorted ascending order. Lets see what I can do with it. Thanks, Robin Don't have 30 days of data but multiple pages of requests are displayed. Verified in 5.10.0.14.20180831154906_2f9a1dd 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-2019:0212 |