Allow using variables when setting up fields for the task created via automation
S
Sanja Djurdjevic
It would be great if we could set priority, assignee, due date and custom fields based on the parameters of the previous task that triggered the automation. If we can use the variables to define task name or description, it would be good if we could, e.g. set a priority based on the Priority variable.
Log In
Traci
This is critical! I hope this is implemented soon.
A
Anthony Biondo
I've had good success with text fields but fields of other types like email don't give you the option to carry the value from another task. ClickUp support said this ticket is the request for this functionality. I reported the issue under ticket #2063739.
Abby Dong
We need this to support our security processes. We create one task related to a security item with a specific due date. We need that due date to be accessible as a variable in an automation to create another task based on certain conditions of the first task.
Example: We hire a new employee. We have a strict requirement to that new employees complete a specific security training within 7 days of their start date. We create onboarding tasks for new employees, and on that task have a custom Date field that lists the employee's start date. We want to take that start date and pass it as a variable to an automation that will add 6 days to the employee's start date and create a new task in a different list on the 6th day to audit their completion of the required security training.
We have other use cases for supporting variables in automations, but this is our most critical one.
Pierre Becher
yes we also need to set custom fields as variables based on the triggering task. duplicate is not an alternative as it would duplicate all fields, however we might only want to carry over a limited number of fields.
Ben Schilling
Would LOVE this for user fields in particular. Being able to assign a task based on a "People" field in another would be killer