Camunda-modeler: Sequence flow condition removed after morphing source or target (Task / Gateway)

[mschoe]

__Describe the Problem__

When changing the source or target of a sequence flow that has a condition configured it seems like re-connecting the sequence flow does not retain the condition.

Steps to Reproduce

• open test diagram
• Change target to intermediate message throw event _or_ change source to inclusive gateway
• See that condition on sequence flow A is lost

__Environment__

Camunda Modeler Version: <= v3.3.0-alpha.1

[nikku]

Adding a condition to the sequence flow should not be allowed (makes no sense from the BPMN perspective).

[nikku]

We have got #131 in the backlog with is not related, right?

[mschoe]

my example was weak. I adjusted the description.

[nikku]

Still an issue with v3.3.0-alpha.1.

[nikku]

I've updated the description to provide more clarity.

[pinussilvestrus]

Seems like this will be fixed by the next release, cf. https://github.com/bpmn-io/bpmn-js/commit/b290078600ae4e45e7c72bd37919732e3f8fcbea

[pinussilvestrus]

Can someone re-check this, so we can add the 'fixed upstream' label? @barmac @philippfromme @oguzeroglu?

[barmac]

I'll have a look at this today.

[oguzeroglu]

@pinussilvestrus I checked this also, this is fixed with the commit you mentioned.

[oguzeroglu]

Closed via Camunda modeler 3.4.0 release.