Unless I’m misunderstanding, the mentioned workaround does NOT work for me because I have a complex rule for when a custom field value is updated. Each unique field value triggers a specific set of actions (comments, add subtasks, etc.).
I can not setup my rule to only trigger when a task is added because none of the automation would run since the automation should happen on existing tasks in the project.
You only need to add “When a Task is added” to reenable the feature. Once you have your desired fields added you can revert to original trigging condition and it will work.
Hi all, quick update on this topic:
Our team is working on a fix which should cover most used cases that were reported. We hope to ship this update around June 17. Thanks for your patience while we work on a resolution.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
Hi everyone, the fix Marie mentioned has been deployed, and we’ve received confirmation from most users that the variables are working well again. If you are still experiencing any issues, please reach out to our Support team. They will be able to look into your specific case in more detail and escalate the issue directly to our Developers if necessary.