-
Notifications
You must be signed in to change notification settings - Fork 638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] Task Listeners #21974
Labels
component/zeebe
Related to the Zeebe component/team
kind/epic
Categorizes an issue as an umbrella issue (e.g. OKR) which references other, smaller issues
version:8.7.0-alpha3
Comments
This was referenced Oct 24, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 9, 2025
## Description <!-- Describe the goal and purpose of this PR. --> With the recently introduced User Task Listeners, a new case arose for Process Instance Migration: migrate the active Task Listener Job when migrating a completing User Task instance. This PR only adds a test case and does not require any production code changes because of the generic job migration implementation of Process Instance Migration. ## Related issues NA relates to: - #17346 - #21974
The feature was released in
|
I'm re-opening this issue, to help track the scope we plan to deliver with 8.8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/zeebe
Related to the Zeebe component/team
kind/epic
Categorizes an issue as an umbrella issue (e.g. OKR) which references other, smaller issues
version:8.7.0-alpha3
Introduction
Currently, Tasklist doesn’t provide any events describing what is happening in tasks.
This blocks technical use cases that require visibility into task state changes, such as managing tasks in a custom task list, assigning users based on custom logic or notifying users about new tasks.
Working with user tasks produces multiple lifecycle events, where each of them might be important to react to. With the current solution, customers need to consume lifecycle events (available only in Self-Managed) in their systems and react to events in a specific way. This is a problem as to satisfy this need customers have to provide additional infrastructure (to consume and store events), filter Zeebe events and react to specific ones. This approach might work only in self-managed installations with a custom Tasklist application.
The lack of this functionality prevents satisfying some HTO use cases where customers need to react to lifecycle events.
This epic addresses the need to unlock multiple human task orchestration use cases.
Task breakdown
✅ Iteration 1
Iteration 1 - Blocking Complete Listener E2E increment - Target End of September
complete
operation #21977✅ Iteration 2
Iteration 2 - Iterate on the complete listener - Target 8.7.0-alpha1
COMPLETE
user task command after task listener execution #23925complete
eventvariables
in Task Listener #24101✅ Iteration 3
Iteration 3 - Assignment listener + listener abilities - Target 8.7.0-alpha2
assignment
task listener #24232action
to compact user task logging #24234✅ Iteration 4
Iteration 4 - Feature wrap up - Target 8.7.0-alpha3
assign
operation (expansion) #24197CLAIMING
event and lifecycle state for User Task #25408action
andpriority
properties in Task Listener #24102Remaining must-have scope - Target 8.8.0-alpha5
updating
event #26934canceling
event #28479Stretch goals
Out of scope
Known bugs
ZeebeTaskListenerEventType.completing
#26809Links
The text was updated successfully, but these errors were encountered: