Bug 1049649 - JBoss BPMS New Task dialog does not work
Summary: JBoss BPMS New Task dialog does not work
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
high
Target Milestone: ER1
: 6.0.1
Assignee: Mauricio Salatino
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-07 23:22 UTC by Pavel Polischouk
Modified: 2016-08-01 01:08 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:03:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
server.log (128.40 KB, text/plain)
2014-01-08 21:53 UTC, Pavel Polischouk
no flags Details

Description Pavel Polischouk 2014-01-07 23:22:27 UTC
Description of problem:
New Task dialog fails to create new tasks on fresh installations of BPMS.

Version-Release number of selected component (if applicable):
JBoss BPMS 6.0.0 ER7 (also present in ER5 and ER6)

How reproducible:
Always

Steps to Reproduce:
1. Make a fresh installation of BPMS ER7, installer or deployable.
2. Log into the business-central GUI.
3. Go to Task List, press New Task button.
4. Enter some task details, press Create button.

Actual results:
The Create button is grayed out, the dialog stays open, the task is not created. This has been tested on Firefox 24.2.0 and Chromium 31.0.1650.63 running on RHEL 6, yielding the same result in both browsers.

Expected results:
The task is created.

Additional info:
This bug is not present in jBPM upstream (latest released version), only in Red Hat BPMS builds.

Comment 1 Kris Verlaenen 2014-01-08 13:10:33 UTC
@Pavel: I just tried this and could not reproduce this on a fresh installation of ER7 (RHEL, FF).  Could you provide more information on:
 - the server.log
 - which user you are logging in with, and the roles he has
 - which details you are filling in the task dialog

@Mauricio: I did notice another issue though, the first task was created with the name I specified in the popup, all subsequent tasks however were created with an empty name

Comment 2 Kris Verlaenen 2014-01-08 13:36:11 UTC
@Mauricio: can't reproduce that second issue anymore either, might have been a clear cache issue.

@Pavel: could you try to make sure you try to clear your cache as well before running the application?

Comment 3 Pavel Polischouk 2014-01-08 21:53:27 UTC
Created attachment 847357 [details]
server.log

Comment 4 Pavel Polischouk 2014-01-08 22:10:09 UTC
@Kris:

I'm using the user admin with the following roles:

admin=analyst,developer,user,manager,admin 

The user was created as part of the installation.

In the task dialog, I enter the task name (something like "test" or "a", no quotes), I tried various options for other fields, like checking or uncheking the 'assign to me' box, changing the User, Priority, Due On. Didn't try changing Advanced options.

I tried cleaning the browser cache, still behaves the same.

Comment 5 Kris Verlaenen 2014-01-08 23:41:05 UTC
There are various issues when performing task operations as user admin in the UI, we will address these for GA2.

Comment 7 Mauricio Salatino 2014-01-27 14:56:50 UTC
Can you please close this issue or mark it related with: https://bugzilla.redhat.com/show_bug.cgi?id=1054309 which is the real issue.

Comment 8 Mauricio Salatino 2014-01-29 20:18:48 UTC
Fixed for hosted mode, in jboss is not happening anymore. You can create tasks for the "admin" user: 

http://github.com/droolsjbpm/kie-wb-distributions/commit/92f51407c
http://github.com/droolsjbpm/jbpm-console-ng/compare/0738506...9bc0f5f

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

Comment 10 Zuzana Krejčová 2014-02-25 14:57:46 UTC
In 6.0.1 ER1, user admin with role/group admin gets error pop-ups when working in Tasks perspective:
"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"
Despite that, such a user can create tasks for other users. Unsurprisingly, he cannot create tasks for himself - this is expected, the sets of user names/logins and of group/role names should be disjoint. A user definitely shouldn't belong to a group with the same name as his user name/login.
With that in mind, I consider this issue fixed.


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