-
-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing test plans in search test plan page #3313
Comments
@mnive can you replicate the same on public.tenant.kiwitcms.org ?
Q2: Do all of the 5 child test plans have the same product as the parent ? Notes: TP-7288 and it's first 4 children have type: Acceptance while TP-7293: Level 5 has a Type of Function. When I filter the search results by Type and select The way child-parent relationships are displayed in the search table is that child rows are groupped together and then hidden from view before the table is rendered: So this looks like an issue with managing expectations because the search table can't show rows which are being filtered out due to the search criteria. I will keep this issue open for now and see if we can idicate that the resulting child-set may not be complete ! |
to let the user know what parent-child hierarchies shown on the page may be incomplete because the data has been filtered out by their search criteria. Closes #3313
HINT: try to reproduce bugs and errors at https://public.tenant.kiwitcms.org!
This is always running the latest version and will automatically submit
traceback and debugging information to us!
Description of problem
In the Search test plan page while expanding the parent plan, some child test plans are not listed in the view
Version or commit hash (if applicable)
12.5
Steps to Reproduce
Actual results
All the test plans are not listed and some test plans are missing in the view.
Click on the parent level test plan and click on expand arrow, all the test plans are listed there.
Expected results
All the test plans should be listed as we expand the parent level test plan
Additional info (Python traceback, logs, etc.)
The text was updated successfully, but these errors were encountered: