Bug 1277962

Summary: REST Query API: taskId_min and taskId_max parameters are reverse
Product: [Retired] JBoss BPMS Platform 6 Reporter: Tomas Livora <tlivora>
Component: Business CentralAssignee: Shelly McGowan <smcgowan>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.2.0CC: lpetrovi, rrajasek
Target Milestone: CR1   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:33:42 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 Tomas Livora 2015-11-04 12:33:23 UTC 
Description of problem:
It seems that taskId_min and taskId_max use reverse condition.

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

Steps to Reproduce:
1. Run some processes with tasks.
2. Try to get tasks using taskId_min and taskId_max parameters.

Actual results:
You get taskId_min behaves like taskId_max should behave and vice versa.

Expected results:
Correct behavior according to the name of the parameter.
Comment 1 Marco Rietveld 2015-11-06 01:49:07 UTC 
Good catch, Tomas, thanks!

PR submitted: https://github.com/droolsjbpm/droolsjbpm-integration/pull/223
Comment 2 Marco Rietveld 2015-11-06 12:52:41 UTC 
Fixed in master. Commits:

master: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/d8039747
Comment 3 Marco Rietveld 2015-11-10 16:16:26 UTC 
Fixed. Commits: 

6.3.x: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/44257bcc

master: 
(see above)
Comment 4 Tomas Livora 2015-11-20 08:49:42 UTC 
Verified on BPMS 6.2.0 CR1