Align search order for user tasks with the new improved search

[GeethaParthasarathy]

Describe the bug

When we search for tasks inside the create/append menu we could see that it is always displayed in the following order of simple tasks and then connector tasks but in case of User task the order is always vice versa

Steps to reproduce

1. Click on the create/append menu
2. Add the search team "form"
3. We could see that the connector tasks are displayed first in the list and then the user task
4. This is not the case for other task types like call activity/business rule tasks where the order is first basic tasks and then connector tasks

Screen.Recording.2025-02-26.at.10.28.32.mov

Expected behavior

Align the search order for user tasks as like other tasks

Environment

• OS: [ MacOS 10.2]
• Camunda Modeler Version: [5.33 rc-1]
• Execution Platform: [Camunda 8]
• Installed plug-ins: [...]

Additional context

No response

[barmac]

The bug might be in one of these:

• https://github.com/bpmn-io/bpmn-js-create-append-anything/tree/main/lib/element-templates
• https://github.com/camunda/camunda-bpmn-js

[nikku]

Or it might be in the core, i.e. PopupMenuComponent.

[Buckwich]

The issue seems to be that the search sorter focuses only on the first key, if that one already gives a difference. This means in most cases only the title is used for sorting, description and search (contains form human) are not relevant for sorting.

Proposed solution (discussed with nikku):

• adjust scoring function to take into account all keys
• support input of string | string [] search items (related to Source additional keywords provided by element templates #4853, which would introduce keywords[])
• (optional) additionally add group for "default" bpmn elements for the case they still score lower

[nikku]

The sr command does not work for me, likely because diagram-js is a dependency of the camunda-modeler/client.

[nikku]

I'm testing now with bpmn-js:

npx @bpmn-io/sr "bpmn-io/bpmn-js" -l "bpmn-io/diagram-js#4856-adjust-result-sorter"  -c 'npm run dev'

[nikku]

@Buckwich Do we have a bigger example in the diagram-js tests in place that allows us to validate this E2E? I could imagine we simply add an integration test there, to be able to verify locally against a "close to real world" example.

[Buckwich]

Do we have a bigger example in the diagram-js tests in place that allows us to validate this E2E? I could imagine we simply add an integration test there, to be able to verify locally against a "close to real world" example.

Not yet as I'm still trying out to find the best search, I think with [] support it would behave like I want it too. I guess I can add some tests just to verify I don't break too much.