Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1264833

Summary:	GetTasksByProcessInstanceIdCommand ignores userId parameter
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Tomas Livora <tlivora>
Component:	Business Central	Assignee:	Shelly McGowan <smcgowan>
Status:	CLOSED EOL	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3.0	CC:	etirelli, kverlaen, lpetrovi, rrajasek
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:	2020-03-27 19:37:18 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-09-21 10:51:48 UTC

Description of problem:
When you try to get tasks for specific user and process instance using GetTasksByProcessInstanceIdCommand, the results will also include tasks for other users.

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

Steps to Reproduce:
1. Run a process with several parallel tasks for different users.
2. Try to get tasks for one of the users by executing GetTasksByProcessInstanceIdCommand.

Actual results:
Also tasks for the other users are included.

Expected results:
Only tasks for the specified user should be there.

Comment 1 Tomas Livora 2015-09-21 11:07:54 UTC

This command is used a lot in our test suite and without this issue being fixed it will take some time to rewrite those tests because we will need to model and use different business processes. So I am marking this as a test blocker.

Comment 2 Marco Rietveld 2015-10-26 14:46:00 UTC

Fixed. Commits: 

6.3.x: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/68a67bd

master: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/fbac57d
https://github.com/droolsjbpm/droolsjbpm-integration/commit/a64f216

* As far as I can tell, this is an issue with the **Remote** API, and not with the actual GetTasksByProcessInstanceIdCommand command. 

If this problem is in reference to use of the task service in an embedded jBPM instance, please add that information in a comment.

Comment 3 Marco Rietveld 2015-10-27 11:20:25 UTC

Oops, please ignore the above comment! There was a mixup.

Comment 5 Tomas Livora 2015-11-04 12:21:27 UTC

I have rewritten our tests not to use GetTasksByProcessInstanceIdCommand so this is no longer a test blocker.

Comment 6 Edson Tirelli 2016-01-04 15:03:21 UTC

Updating flags to reflect current status.