| Summary: | Task List - when no tasks are in the list the Details section should not be present | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Tihomir Surdilovic <tsurdilo> |
| Component: | Business Central | Assignee: | Mauricio Salatino <msalatin> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Livora <tlivora> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.0 | CC: | jpaulraj, kverlaen, mbaluch, paradhya, rrajasek |
| Target Milestone: | CR1 | ||
| Target Release: | 6.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-06 20:10:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Tihomir Surdilovic
2013-12-12 23:26:30 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. 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. *** Bug 1049397 has been marked as a duplicate of this bug. *** Since the behavior obsesrved in a duplicate was considered a blocker, requesting flag here as well. fixed in 6.0.x: https://github.com/droolsjbpm/jbpm-console-ng/commit/8203397ef516835c6bed2042e58e0a37a35dab0e https://github.com/droolsjbpm/jbpm-console-ng/commit/8203397ef516835c6bed2042e58e0a37a35dab0e Verified on BPMS 6.0.0 CR1 |