Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1278756

Summary: Isn't possible to move group of elements from container
Product: [Retired] JBoss BPMS Platform 6 Reporter: Kirill Gaevskii <kgaevski>
Component: jBPM DesignerAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED DUPLICATE QA Contact: Kirill Gaevskii <kgaevski>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.2.0CC: etirelli, lpetrovi
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-12 15:58:37 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1275339    
Attachments:
Description Flags
Not possible to disassign group of elements from container none

Description Kirill Gaevskii 2015-11-06 11:06:45 UTC 
Created attachment 1090609 [details]
Not possible to disassign group of elements from container

Description of problem:
If you select group of element (or all of them) on the container and move it out of container all associations will be not updated - all moved elements will be still associated with this container. (See attachment)

Version-Release number of selected component (if applicable):
6.2.ER5

How reproducible:
always

Steps to Reproduce:
1. Create process with container (Swimlane or Subprocess)
2. Put some elements to the container (for example StartEvent->Task->EndEvent)
3. Select at least two of them
4. Move this elements out of container

Actual results:
All elements will be associated with container

Expected results:
All moved elements will lose it's association with container

Additional info:
If you will move just one element it will lose it's association as expected.

It is regression relatively to 6.2.ER4

Maybe it is related to bug 1273324
Comment 1 Edson Tirelli 2015-11-12 14:30:51 UTC 
Raising priority to urgent as discussed by e-mail.
Comment 2 Tihomir Surdilovic 2015-11-12 15:58:37 UTC 
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1275339. Same fix applies.

*** This bug has been marked as a duplicate of bug 1275339 ***