Hide Forgot
Description of problem: I have a reserved task in Tasks list but I'm not able to start it. The Start button doesn't do anything after a click. Server log says nothing. How reproducible: Steps to Reproduce: 1. Start a process containing a human task 2. In Business central switch to Tasks list view 3. Use workaround, described here BZ 1034242, to show the reserved task 4. Click on the start button 5. See nothing happens
I also tried the Start button in the task details but it didn't help either.
Created attachment 828688 [details] The start task REST response I attached a response from a REST request to start the task.
Hi Ivo, can you please confirm that you are not using the admin user? You shouldn't test with that, please use another user and let me know if it continue failing. I will not start working on this or the other bug if the problem is that the test were done with the admin user.
Hi Mauricio, would mind explaining why exactly should the 'admin' user not be user for these actions? I'd say that the 'admin' user is a user like any other if he has the proper roles assigned. Thanks! @mb
If the reason is the database table design then we can document it if not already documented.
Hi Mauricio, you're right. After I changed the user, human tasks work, so the problem is just for the admin.
Hi Marek, as you mention the issue is that all the Task UI is ready to deal with standard users and admin is a special kind of user. You should avoid testing tasks and processes with that user that in theory is supposed to do another kind of global things and configurations. This should be already documented, because we had closed issues about two or more months ago of people doing the same tests and finding the same errors.
I will mark this issue as modified, due Ivo has confirmed that the issue is not longer there if he tried with a regular user.
Mauricio, I wouldn't set this to modified, as the original issue is still there, I lowered the priority to medium, though, as it only seems to occur for admin users.
If it's not documented, we should put there that a user should not use "admin" as a username. Otherwise the user will have issues like this BZ 1034258, BZ 1034242, and BZ 1034608.
Can you please close this issue or mark related with: https://bugzilla.redhat.com/show_bug.cgi?id=1054309 which is the real issue.
Mauricio, I do not think this issue relates to bug 1054309 and it should not be closed. Here the task is assigned to the same user "admin" and the main problem here is that the user "admin" has role "admin" as was mentioned above. The another difference is that in this bug it is not possible to start a process and in the second bug the task list does not show all tasks for a user with role "admin". If you still think they relate to each other, connect them.
This issue is not longer in KIE-WB 6.0.x, i've fixed the issue also in hosted mode: https://github.com/droolsjbpm/jbpm-console-ng/commit/9bc0f5fbcec225e54f3de2ec6ab92b258d52da5c https://github.com/droolsjbpm/kie-wb-distributions/commit/92f51407c5e8e4a9b7360f6280f677b30770a61a
This no longer has a target release of 6.0.0.
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
Test that a user is notified about using a username which is equal to a group (e.g. admin/admin).