Does anyone know of any existing capability for variable functionality within the custom fields? This is currently a big gap.
Could you clarify what you mean with variable functionality in custom fields?
What is the why behind your request?
Also, if we can move this to Tips and Tricks a lot more people can chime in.
Sure- there’s no current way (that I’m aware of) to use a rule to pull over custom fields into the custom fields of another task (or subtask). You can only use the variable option to populate that into text fields (task name, task description, comments etc).
Here’s an example (below). There’s no way to instead “set task [custom field] to ___” and then be able to select a variable.
1 Like
For me it is possible for text fields:
Would you want to do this for other custom fields?
Also, I’m still not sure why you’d want this. If you can explain what the outcome is that you are after, using as little Asana terminology as possible, we might be able to help find a workaround.
Yes, I’d like to see it for other custom fields (single-select and multi-select fields).
This would help for an intake form where we would want to form submissions to come in as more than 1 task. We have existing intake forms where users can select more than 1 item and need each thing to come in as separate tasks but retain the same collection of information.
FYI you can do this using the rules in our Flowsana integration. Depending on the specific use case, it usually involves taking advantage of our Variable Substitution capability.
1 Like
2 Likes