Adding Message Flows to Pool Boundaries is Tricky When Pool Once Had More Than One Lane

[sebwarnke]

Describe the Bug

When I try to connect a message flow to the boundary of a pool that had more than one lane this is only possible by dropping the connector at the header of the pool; not anymore inside the single lane of the pool

Steps to Reproduce

Steps to reproduce the behavior:

1. Create two pools
2. Connect both pools using the connector tool by clicking first in one pool's body and then in the other pool's body
3. Add an additional lane to one of the pools
4. Remove that lane right away
5. Repeat step 2.

Expected Behavior

I can connect both pools like I did in step 2.

Environment

Please complete the following information:

• Camunda Modeler 2.2.4
• Camunda Modeler 3.0.0-beta.3.3358

[pinussilvestrus]

This relates to an issue reported inside the Camunda Modeler (camunda/camunda-modeler#1213).

This could be a little nice improvement in terms of UX. Maybe it's worth it to put it inside the next milestone. What do you think @nikku?

[nikku]

Our next milestone is huge already 😉.

Let's queue this in our backlog for now.

[pinussilvestrus]

Closed via 19be51a