Bug 1279782

Summary: Version history table paging broken
Product: [Retired] JBoss BRMS Platform 6 Reporter: Jiri Locker <jlocker>
Component: Business CentralAssignee: Toni Rikkola <trikkola>
Status: CLOSED DUPLICATE QA Contact: Jiri Locker <jlocker>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-10 12:08:28 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:

Description Jiri Locker 2015-11-10 09:58:36 UTC 
Description of problem:
When asset has 6 or more revisions (commits), the table paging becomes effective. The first page is limited to 5 revisions, however the second page is empty. It remains empty until there is 11+ revisions. Then first page has five latest revision, the other five revisions are skipped and the second (last) page contains remaining revisions.

It seems that paging starts working correctly when there is more than 20 revisions.

Version-Release number of selected component (if applicable):
6.2.0.ER5

How reproducible:
-

Steps to Reproduce:
1. Create new DRL file, save it 5 times to reach 6 revisions.
2. Switch to overview, table paginator says 1-5 of 6.
3. Move to next page.

Actual results:
The second page is empty, paginator says 11 of 6.

Expected results:
The second page should contain 1 row with the initial commit, paginator should say 6 of 6.
OR, similar result if the page limit changes with the fix (e.g. to 10).

Additional info:
Comment 1 Toni Rikkola 2015-11-10 12:08:28 UTC 

*** This bug has been marked as a duplicate of bug 1273036 ***