Smooth 8.7 migration linting: mixed-user-task-impl

[Skaiir]

Supports https://github.com/camunda/product-hub/issues/2126.

The rule should detect the following modeling patterns

Mixed use of job workers and zeebe user tasks

• Incorrect

    <bpmn:userTask id="Activity_18h160l" name="Job worker">
    </bpmn:userTask>
    <bpmn:userTask id="Activity_18h160l" name="Job worker">
      <bpmn:extensionElements>
        <zeebe:userTask />
      </bpmn:extensionElements>
    </bpmn:userTask>

• Correct

    <bpmn:userTask id="Activity_18h160l" name="Job worker">
    </bpmn:userTask>
    <bpmn:userTask id="Activity_18h160l" name="Job worker">
    </bpmn:userTask>

OR

    <bpmn:userTask id="Activity_18h160l" name="Job worker">
      <bpmn:extensionElements>
        <zeebe:userTask />
      </bpmn:extensionElements>
    </bpmn:userTask>
    <bpmn:userTask id="Activity_18h160l" name="Job worker">
      <bpmn:extensionElements>
        <zeebe:userTask />
      </bpmn:extensionElements>
    </bpmn:userTask>

How does the rule improve the BPMN diagram?

With the deprecation of user tasks soon, and since it can be generally challenging to mixed implementations, we should discourage it via warnings, but not outright error it as it somewhat supported (for now anyways).

Rule Details

• Name: mixed-user-task-impl
• Default notification level: error|warn|off

What alternatives did you consider?

n/a

[Skaiir]

Relating to https://github.com/camunda/product-hub/issues/2126

[nikku]

@Skaiir I guess you'll still work on this?