[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1438) Task assigned to different actor-id can be seen and manipulated in jBPM console

[Alejandro Guizar (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBPM-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12424124#action_12424124 ] 

Alejandro Guizar commented on JBPM-1438:
----------------------------------------

Ronald resolved the task list issue in jBPM 3.2.3, by popular demand. See JBPM-1022. I guess the change was not applied to the SOA branch. This should be addressed in the upcoming 3.3 release. I am marking this issue as duplicate instead.

> Task assigned to different actor-id can be seen and manipulated in jBPM console
> -------------------------------------------------------------------------------
>
>                 Key: JBPM-1438
>                 URL: https://jira.jboss.org/jira/browse/JBPM-1438
>             Project: JBoss jBPM
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core Engine
>    Affects Versions: jPDL 3.2.2
>         Environment: JBossESB server 4.3.GA, bpm_orchestration4
>            Reporter: Martin Vecera
>            Assignee: Tom Baeyens
>
> By default JBossESB server 4.3.GA has several jBPM users configured including 'user' and 'manager'.
> bpm_orchestration4 example contains one process definition which assigns two tasks, first to actor-id 'user' and the second to actor-id 'manager'.
> The problem is that the 'user' can see and manipulate both of the tasks.
> Steps to reproduce:
> 1. download JBossESB server 4.3.GA
> 2. start it using bin/run.sh
> 3. go to samples/quickstarts/bpm_orchestration4
> 4. run one by one: ant deploy, ant deployProcess, ant startProcess
> 5. open jBPM console and login as 'user' with password 'user'
> 6. click on Tasks to see the task list and on Examine to open the task, then on Save and Close
> 7. refresh the task list and you can see second task assigned to 'manager', try to Examine it...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira