Bug 1739737
| Summary: | One should be taken to page 1 of result page after filtering saved reports | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Nandini Chandra <nachandr> |
| Component: | UI - OPS | Assignee: | Milan Zázrivec <mzazrivec> |
| Status: | POST --- | QA Contact: | Nandini Chandra <nachandr> |
| Severity: | high | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Priority: | medium | ||
| Version: | 5.11.0 | CC: | bmidwood, hkataria, lavenel |
| Target Milestone: | GA | ||
| Target Release: | 5.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | Bug | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | CFME Core | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Nandini Chandra
2019-08-09 22:40:03 UTC
I have problems understanding the report.
> For eg: Use the paginator to get to any page other than page 1 of a multi page report. Search for a string and the search doesn't find a match even if there is a matched string on that page.
Do you mean that if there's a match on 2nd page and you execute search, then the match is not found? This works for me well.
Also the search goes throught the API, see the browser tools network tab. If something is not found is it returned by the API? So you see the results in the browser tools and not on the screen?
Can you, please, provide more concrete steps or video or screenshots?
I guessed (with help of Martin Hradil), that the problem is that after filtering one is not navigated to page 1 of the results. A fix for that is here: https://github.com/martinpovolny/manageiq-ui-classic/pull/new/report_filter_page1 Please, confirm that that is the issue that was reported. Thx! correct URL of the PR: https://github.com/ManageIQ/manageiq-ui-classic/pull/6001 Hey Martin, You are correct. The search results are on page 1, and if you are on any page other than that, you won't be able to see the results, until and unless you navigate to page 1. I don't think it's really a bug, but an improvement to this feature would be nice. Thanks, Parthvi New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/27f7b8e158720b07b26cfe67be9eaaa4c5d0ec6c commit 27f7b8e158720b07b26cfe67be9eaaa4c5d0ec6c Author: Martin Povolny <mpovolny> AuthorDate: Tue Aug 13 06:32:59 2019 -0400 Commit: Martin Povolny <mpovolny> CommitDate: Tue Aug 13 06:32:59 2019 -0400 Report results: after filterin, go to page 1. Related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1739737 app/javascript/components/report-data-table.jsx | 7 +- 1 file changed, 6 insertions(+), 1 deletion(-) (In reply to Martin Povolny from comment #3) > I guessed (with help of Martin Hradil), that the problem is that after > filtering one is not navigated to page 1 of the results. > > A fix for that is here: > https://github.com/martinpovolny/manageiq-ui-classic/pull/new/ > report_filter_page1 > > Please, confirm that that is the issue that was reported. > > Thx! Hi Martin, Wow, I didn't realize that the search results were actually on two different pages. After, I ran the search, it did take me to page 2 and not page 1.That is the bug I encountered. The search result listed just seven items. With 100 items/page, I don't understand why there should be a 2 page result when the seven items could be fitted in one page. Thanks for the fix. |