# Asana Release Notes January 2026

**URL:** <https://forum.asana.com/t/asana-release-notes-january-2026/1121661>\
**Category:** Release Notes\
**Created:** [30 January 2026 17:23 UTC](https://forum.asana.com/t/asana-release-notes-january-2026/1121661 "2026-01-30T17:23:14Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Elizabeth\_Lumsden](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/elizabeth_lumsden/32/290448_2.png) [@Elizabeth\_Lumsden](https://forum.asana.com/u/Elizabeth_Lumsden)\
**Post date:** [5 February 2026 18:27 UTC](https://forum.asana.com/t/asana-release-notes-january-2026/1121661/6 "2026-02-05T18:27:24Z")

</div>

> [@Vanessa\_N](#):
>
> - **(Starter) Reference custom fields in rules - action:** Rules can now use reference custom fields in actions so automations can update or connect related work based on linked records.

I see the conditions based on this are simply “is empty” or “is not empty,” while actions can add to, set to, or clear. I was hopeful this might be a workaround resolution to a feature request we’re interested in ([ability to set a condition in rules: Check If task is in project](https://forum.asana.com/t/ability-to-set-a-condition-in-rules-check-if-task-is-in-project/794680)), but it isn’t. I can’t check if the reference field contains or does not contain a specific project and take action accordingly. Hoping for this functionality at some point to create better, efficient connections between multiple flows where tasks are multi-homed along the way.

---

_[View the full topic](https://forum.asana.com/t/asana-release-notes-january-2026/1121661)._
