Bug 1034242 - Human tasks are not visible in the view until a view is changed
Summary: Human tasks are not visible in the view until a view is changed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ER1
: 6.0.1
Assignee: Mauricio Salatino
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-25 13:26 UTC by Ivo Bek
Modified: 2014-11-12 14:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:03:35 UTC
Type: Bug


Attachments (Terms of Use)
screenshot1 (42.44 KB, image/png)
2013-11-25 13:27 UTC, Ivo Bek
no flags Details
screenshot2 (42.33 KB, image/png)
2013-11-25 13:27 UTC, Ivo Bek
no flags Details
screenshot3 (40.08 KB, image/png)
2013-11-25 13:30 UTC, Ivo Bek
no flags Details
screenshot4 (41.96 KB, image/png)
2013-11-25 13:31 UTC, Ivo Bek
no flags Details
the process definition with a human task (7.90 KB, application/xml)
2013-11-26 08:17 UTC, Ivo Bek
no flags Details

Description Ivo Bek 2013-11-25 13:26:50 UTC
Description of problem:

When I run a business process containing a human task, the task is not visible in the tasks list until I change a view to personal. After that the task will appear. Even refresh button doesn't refresh the list. I'll attach 4 screenshots how the list looks after each step. 

How reproducible:


Steps to Reproduce:
1. Start a process containing a human task.
2. In Business central switch to tasks list view
3. See there is no task to be performed (screenshot1)
4. Refresh the list (screenshot2) - still nothing appears
5. Change the view to personal or any other than current active (screenshot3) - the task will appear
6. Change back to the active view to ensure it's not just in other view (screenshot4)

Actual results:


Expected results:


Additional info:

Comment 1 Ivo Bek 2013-11-25 13:27:31 UTC
Created attachment 828673 [details]
screenshot1

Comment 2 Ivo Bek 2013-11-25 13:27:56 UTC
Created attachment 828674 [details]
screenshot2

Comment 3 Ivo Bek 2013-11-25 13:30:17 UTC
Created attachment 828675 [details]
screenshot3

Comment 4 Ivo Bek 2013-11-25 13:31:19 UTC
Created attachment 828677 [details]
screenshot4

Comment 5 Mauricio Salatino 2013-11-25 20:27:26 UTC
can you please attach the process that you are using? 
I've noticed that you are using the Admin user.. please avoid doing that.. can you try again with a regular user? like katy or salaboy?

Comment 6 Ivo Bek 2013-11-26 08:17:10 UTC
Created attachment 829095 [details]
the process definition with a human task

Comment 7 Ivo Bek 2013-11-26 08:58:05 UTC
After I used a regular user (ibek), the human task appeared in the view immediately after I opened it, so the problem is just for the admin.

Comment 8 Mauricio Salatino 2013-11-26 09:21:36 UTC
Ok, I'm marking this BZ as Modified based on Ivo's confirmation.

Comment 9 Marek Baluch 2013-12-09 10:05:32 UTC
This should not be on MODIFIED state as no work has been done.

Comment 10 Mauricio Salatino 2014-01-31 17:28:22 UTC
This issue is already fixed in 6.0.x, here are the fixes for hosted mode in both the jbpm console and the kie workbench:

https://github.com/droolsjbpm/jbpm-console-ng/commit/9bc0f5fbcec225e54f3de2ec6ab92b258d52da5c


https://github.com/droolsjbpm/kie-wb-distributions/commit/92f51407c5e8e4a9b7360f6280f677b30770a61a

Comment 11 Lukáš Petrovický 2014-02-07 16:19:14 UTC
This no longer has a target release of 6.0.0.

Comment 12 Ivo Bek 2014-02-20 12:16:03 UTC
Verified in BPMS 6.0.1.ER1

I assume it is expected to show the error dialog containing:

Unexpected error encountered : java.lang.RuntimeException:Organizational entity already exists with [GroupImpl:'admin'] id, please check that there is no group and user with same id

Comment 13 Ivo Bek 2014-03-18 13:01:45 UTC
Test that a user is notified about using a username which is equal to a group (e.g. admin/admin).


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