Skip to content
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

I can access the assignee of a completed user task or user form #18510

Open
saig0 opened this issue May 14, 2024 · 0 comments
Open

I can access the assignee of a completed user task or user form #18510

saig0 opened this issue May 14, 2024 · 0 comments
Assignees
Labels
component/zeebe Related to the Zeebe component/team kind/feature Categorizes an issue or PR as a feature, i.e. new behavior

Comments

@saig0
Copy link
Member

saig0 commented May 14, 2024

Is your feature request related to a problem? Please describe.
I have a process with a sequence of user tasks. The user tasks don't have a fixed assignee, either unassigned or with candidate users/groups. The user who completed the first user task A should work on the follow-up user tasks B and C.

Screenshot from 2024-05-14 15-00-30

Currently, I can't use the user of the completed task A as the assignee of task B. The user needs to assign themself.

A similar problem exists if the process is created by a user form in Tasklist. In this case, the user who filled out the user form should work on the next task A.

Describe the solution you'd like
I can access the assignee of a completed user task and store it in a process variable to use it as the assignee for a follow-up user task.

💡 Idea: I can access the assignee of the user task in the output mapping of the user task. For example, by using the expression context (ref): = camunda.user_task.assignee.

For user start forms: I can access the user of a completed user start form and store it in a process variable to use it as the assignee for a follow-up user task.

Describe alternatives you've considered

  • The user needs to assign themself every time - Error-prone + a lot of clicks
  • Use the Tasklist API to fetch the completed user task - Complicated + pollute the process

Additional context
This feature is relevant for user-driven/-focused processes, for example, in an end-to-end release process.

@saig0 saig0 added kind/feature Categorizes an issue or PR as a feature, i.e. new behavior component/zeebe Related to the Zeebe component/team labels May 14, 2024
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/feature Categorizes an issue or PR as a feature, i.e. new behavior
Projects
None yet
Development

No branches or pull requests

2 participants