Bug 1256791 - Contributors persp.: Table disappears when using pager and then filtering
Summary: Contributors persp.: Table disappears when using pager and then filtering
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: BAM
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ER5
: 6.2.0
Assignee: David Gutierrez
QA Contact: Gui Jospin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-25 12:48 UTC by Jan Hrcek
Modified: 2020-03-27 20:03 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:03:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Video illustrating the issue and steps to reproduce (1.88 MB, application/octet-stream)
2015-08-25 12:48 UTC, Jan Hrcek
no flags Details
exception from server.log (7.38 KB, text/plain)
2015-08-25 12:52 UTC, Jan Hrcek
no flags Details

Description Jan Hrcek 2015-08-25 12:48:49 UTC
Created attachment 1066841 [details]
Video illustrating the issue and steps to reproduce

Description of problem:
In contributors perspective: 

When filtering select is used to filter the commits AND the user has navigated the table to some different page (using table paging) the table disappears and the following error appears instead: ERROR: java.lang.Throwable: offset can't be greater than the number of rows: 20

Looks like some table paging issue.

Version-Release number of selected component (if applicable):
BPM Suite 6.1.0 ER1

How reproducible:
Always

Steps to Reproduce:
1. Start business-central (let it setup the default jbpm-playground  - default settings)
2. Navigate to contributors perspective
3. Use pager to move to Table page 4 or more
4. Filter based on Author (e.g. Kris - or someone who has less commits that the commits that fit on the currently displayed table page)

Actual results:
Exception in server.log: java.lang.IllegalArgumentException: Offset can't be greater than the number of rows: 20 (full stact trace in attachment).

When user click "next" in the table pager, this error also appears in UI.

Expected results:
Page should probably be reset to the first page when filtering via selects and no exception should be thrown.

Additional info:

Comment 1 Jan Hrcek 2015-08-25 12:52:59 UTC
Created attachment 1066842 [details]
exception from server.log

Comment 2 David Gutierrez 2015-10-13 14:46:08 UTC
Same issue has been reported in the community JIRA:

https://issues.jboss.org/browse/DASHBUILDE-49

Comment 3 David Gutierrez 2015-10-15 14:57:04 UTC
The related JIRA has been fixed.

Tested and verified on business-central following the same steps as explained above.

Comment 4 Jan Hrcek 2015-11-03 13:21:50 UTC
Ok, this is working correctly now. Verified with BPM Suite 6.2.0 ER5


Note You need to log in before you can comment on or make changes to this bug.