Bug 1019689 - Problems panel cannot be effectively closed when editing a process in the Designer
Summary: Problems panel cannot be effectively closed when editing a process in the Des...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: CR2
: 6.0.0
Assignee: Tihomir Surdilovic
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-16 09:13 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:08 UTC (History)
3 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1006943 0 high CLOSED Closing Problems tab reloads the Designer, discarding all changes 2021-02-22 00:41:40 UTC

Internal Links: 1006943

Description Zuzana Krejčová 2013-10-16 09:13:50 UTC 
Description of problem:
When you're working on a process in the Designer and try to close the Problems panel, it reloads the Designer. Immediately after the Designer reloads, the Problems panel either pops up again or there is blank space left where it used to be before it was closed.

It doesn't matter whether the process is valid or invalid.


Version-Release number of selected component (if applicable):
BPMS 6.0 ER4
Comment 1 Kris Verlaenen 2014-02-03 15:35:16 UTC 
This seems to be fixed on CR2, I could successfully close the problems view now without it being reopened (after designer reloaded).
Comment 2 Zuzana Krejčová 2014-02-04 09:09:45 UTC 
(In reply to Kris Verlaenen from comment #1)
> This seems to be fixed on CR2, I could successfully close the problems view
> now without it being reopened (after designer reloaded).

You're right, verified in CR2. Thanks for checking this.
Comment 3 Lukáš Petrovický 2014-02-07 16:15:47 UTC 
This BZ has been part of the 6.0.0 stream.
Note You need to log in before you can comment on or make changes to this bug.