-
Bug
-
Resolution: Done
-
Critical
-
6.1.0
-
None
+++ This bug was initially created as a clone of Bug #1232975 +++
Description of problem:
If we have a gateway in Swimlane1 and it is connected to tasks on Swimlane2, all the time we chance Swimlane1 position or swimlane 2 position, the connectors position changes, making hard to check where its connection ends. (which node)
Version-Release number of selected component (if applicable):
n/a
How reproducible:
Always
Steps to Reproduce:
1. Create a process in a new project in BPM Suite 6.1
2. add a start node that is connected to a task which is connect to a gateway
3. Connect the gateway to tasks in another gateways and adjust the connector position (direction)
Actual results:
Every time we move the swimlane, it changes the connector position back to a default position
Expected results:
Do no change the position.
Additional info:
See attachments that demonstrate this issue.
— Additional comment from William Antônio on 2015-06-17 20:34:07 EDT —
— Additional comment from JBoss Product and Program Management on 2015-06-17 20:40:06 EDT —
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
- duplicates
-
RHBPMS-169 Process elements divided in different swimlanes changes its connectors positions everytime we move one of the swimlanes
- Verified
- is blocked by
-
RHBPMS-169 Process elements divided in different swimlanes changes its connectors positions everytime we move one of the swimlanes
- Verified