Nico Rehwaldt

@YanaSegal Thanks for your answer. Showing (all) incompatible templates in the create/replace/append menu could have negative effects, because as a general mechanisms a lot of upgrading or downgrading hints will...

@Skaiir the direction you proposed sounds reasonable and https://github.com/bpmn-io/diagram-js/pull/987 is the stable foundation we need. As you mentioned, we need to be able to customize what element template is shown,...

I'd be interested how we solve the following issue: * There is a compatible version of template `` * There is also a new version of template `` that is...

Not sure if I got your point. But my strong recommendation would be: * We don't show future version of `AI agent` in the create/append anything menu if a current...

> @nikku Yeah implementation wise this is what I'm going to do. UX wise we agree: Append menu is not the tool to drive updates. The properties panel and potentially...

CC @mschoe (we discussed and detected this issue).

@abdul99ahad is the solution already integrated into the modeler? If not, please move this issue to _fixed upstream_, and work towards the integration of the fixed upstream library.

@misiekhardcore Where else could we anchor the element template selector, so we don't have to move Zeebe execution listeners?

You mean this? > We still want to display the execution listeners above the template when it's applied, correct? What would be practical reasons to put execution listeners above the...

This issues is not closed by https://github.com/bpmn-io/bpmn-js-element-templates/pull/130, but instead awaits integration of the upstream change to be fixed. I re-opened and attached `fixed upstream` to it.