Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
False
-
NEW
-
NEW
Description
When implementing TaskLifeCycleEventListener interface the following behaviour is observed:
1. beforeTaskAddedEvent --> task_status = null
2. afterTaskAddedEvent --> task_status = Ready (or Reserved when autoclaim)3. beforeTaskActivatedEvent --> task_status = Ready (or Reserved when autoclaim)
4. afterTaskActivatedEvent --> task_status = Ready (or Reserved when autoclaim)From the above, the task status "Created" is not shown at all. However, the expected behaviour would be:
1. beforeTaskAddedEvent --> task_status = null
2. afterTaskAddedEvent --> task_status = Created3. beforeTaskActivatedEvent --> task_status =Created
4. afterTaskActivatedEvent --> task_status = Ready (or Reserved when autoclaim)
Attachments
Issue Links
- clones
-
RHPAM-3934 Event types in the TaskLifeCycleEventListener interface do not match with human task life cycle status
- Closed