Bug 1042520 - Task List - when no tasks are in the list the Details section should not be present
Summary: Task List - when no tasks are in the list the Details section should not be p...
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: CR1
: 6.0.0
Assignee: Mauricio Salatino
QA Contact: Tomas Livora
URL:
Whiteboard:
: 1049397 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 23:26 UTC by Tihomir Surdilovic
Modified: 2014-08-06 20:10 UTC (History)
5 users (show)

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


Attachments (Terms of Use)

Description Tihomir Surdilovic 2013-12-12 23:26:30 UTC
In the task list when all tasks complete, the Details section should be removed (currently it shows just empty values which is confusing).

Comment 3 Prakash Aradhya 2013-12-19 15:45:52 UTC
I am OK to push this off to 6.0.1
But this a must fix for 6.01.  This puts us in an embarrassing situation in front of customers when demoing the product.  
I have heard comments like product is not mature and has design flaws.

I really really do not want this to be punt out beyond 6.0.1.
Kris / Mauricio I appreciate you start looking at a viable solution for this at the earliest.
And please consult UX team also.

Comment 4 Mauricio Salatino 2014-01-02 21:21:19 UTC
Hi Guys, 
I've fixed in master and 6.0.x this issue, so the panel never shows empty data. But there are some situations where the panel can remains open when there are no tasks in the task lists. The task list can be empty because the filters didn't return any result, but there are some cases where  the user can have previously selected an existing task. In such cases, keeping the task details opened is valid. 

Once again, I agree that showing the task details without any information is a bug and that must be fixed. 

I will double check the solution now, because there are tons of edge cases which can cause a failure. For the release after 6.0.1 I would like to refactor the internals to avoid all these edge cases which are caused by how the tasks are being handled internally.

Comment 5 Kris Verlaenen 2014-01-08 13:23:10 UTC
*** Bug 1049397 has been marked as a duplicate of this bug. ***

Comment 6 Kris Verlaenen 2014-01-08 18:33:58 UTC
Since the behavior obsesrved in a duplicate was considered a blocker, requesting flag here as well.

Comment 8 Tomas Livora 2014-01-24 11:12:17 UTC
Verified on BPMS 6.0.0 CR1


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