-
Enhancement
-
Resolution: Done
-
Major
-
jBPM 5.2
Currently escalation (reassignment) replaces potential owners but does not remove actual owner, which in turn causes tasks not accessible in jbpm-console.
According to spec, after reassignment tasks should be put in ready state (which means no actual owner yet) with replaced potential owners.
- is related to
-
JBPM-3575 Deadline/escalation support for user task nodes
- Resolved