Description of problem: On the Manage Search page, there is an empty "Current Progress" section down the bottom. If th euser clicks "Perform Selected Actions" it shows a different page for the progress, so this sections seems unused. Version-Release number of selected component (if applicable): 3.3.0 RC1 How reproducible: Easy always Steps to Reproduce: 1. Sign in as admin, click drop-down menu > Administration 2. Select Manage Search 3. Select some items. Note the "Current Progress" section" 4. Press Perform Selected Actions Actual results: A new screen with a progress bar Expected results: If it isn't supposed to show inline then the extra section is not necessary Additional info:
Previously, the "Current Progress" section would have content that indicated either that no operations had been run since the last server restart, current progress of an operation, or the results of the last operation (success or failure). This seems to have been changed. Technically this is all happening on the same page - the table is just hidden when the search is in progress. The fix should just be to hide the "Current Progress" heading when no action is in progress.
(In reply to David Mason from comment #1) > Previously, the "Current Progress" section would have content that indicated > either that no operations had been run since the last server restart, > current progress of an operation, or the results of the last operation > (success or failure). This seems to have been changed. > > Technically this is all happening on the same page - the table is just > hidden when the search is in progress. The fix should just be to hide the > "Current Progress" heading when no action is in progress. On inspection of the code, it looks like the information under "Current Progress" is still supposed to be displayed, but is not being rendered.
I have updated the display for reindexing status to be compatible with JSF 2 so that status is displayed. Elapsed time and time estimates are not being displayed pending pending some backend changes. I will track this separately in https://bugzilla.redhat.com/show_bug.cgi?id=1065790 See: https://github.com/zanata/zanata-server/commit/e8147cdb0c2b0b42263a21602f8e02bfb6872b03
Which pull request was this? And should we set target release to 3.3?
https://github.com/zanata/zanata-server/pull/378
Verified at 1bf60cc19d6941929f586c3e8d62390fbb41644d
Closing VERIFIED bugs for Zanata server 3.3.2.