UserTask's timeoutListenerDeclaration will be deleted from processDefinitionImpl after migrate

[FeiyuEVE]

Environment (Required on creation)

camunda 7.19.0
springboot 2.7
java 11

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)

This line will remove timerDeclaration from processDefinition

camunda-bpm-platform/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java

Line 130 in 47c0504

TimerDeclarationImpl declaration = activityDeclarations.remove(((TimerJobConfiguration) jobHandlerConfiguration).getTimerElementSecondaryKey());

Because shallow copy at

camunda-bpm-platform/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java

Line 52 in 47c0504

Map<String, Map<String, TimerDeclarationImpl>> targetTimeoutListenerDeclarationsInEventScope = new HashMap<>(TimerDeclarationImpl.getTimeoutListenerDeclarationsForScope(activityInstance.getTargetScope()));

targetTimeoutListenerDeclarationsInEventScope's inner map —— targetTimerDeclarations points to targetTimerDeclarations which is belong to userTask of processDefinition

Steps to reproduce (Required on creation)

1. create processDefinition with multi-instance userTask (will produce 2 userTasks at least) and the userTask has a timeoutListener
2. start it
3. deploy the processDefinition again to produce a new version
4. migrate the processInstance to new version
5. the first userTaskInstance will migrate timeoutJob successfully but the rest of userTaskInstance's timeoutJob will be deleted because timerDeclaration been deleted

Observed Behavior (Required on creation)

Expected behavior (Required on creation)

Root Cause (Required on prioritization)

Solution Ideas

Hints

Links

Breakdown

Pull Requests

Beta Give feedback

No tasks being tracked yet.

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[venetrius]

Hi @FeiyuEVE,

Thanks for raising this bug issue. I will try to reproduce it and will get back to you.