# Project-Scoped Lookup Fields

**URL:** <https://forum.asana.com/t/project-scoped-lookup-fields/1161942>\
**Category:** Product Ideas\
**Tags:** lookup-fields, agentic-work-management\
**Created:** [17 November 2026 20:10 UTC](https://forum.asana.com/t/project-scoped-lookup-fields/1161942 "2026-11-17T20:10:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nick\_Q](https://luna1.co/8d76cd.png) [@Nick\_Q](https://forum.asana.com/u/Nick_Q)\
**Post date:** [17 November 2026 20:10 UTC](https://forum.asana.com/t/project-scoped-lookup-fields/1161942/1 "2026-11-17T20:10:23Z")

</div>

It would be incredible to have lookup fields work with project-scoped reference fields, especially with interlinked request processing projects.

As an example, I have a contract processing project and an invoicing processing project. When a contract is signed, I can create one or more invoices from the contract task and track that workflow in a separate project. My colleagues have a view which allows them to see all the contracts they are working on. One difficulty is filtering out invoices. They want to see the invoices for all active contracts regardless of their status (not sent, paid, etc.) This requires me to have a custom field that is manually updated when the contract has expired.

With a project-scoped lookup field, I could pull the contract status directly onto each of the invoice tasks. It could then be used to automate filters, etc.

I can think of many more applications for something like this. I bet lots of folks have had the thought while building projects: “If only I could have a rule trigger based on a different task”. Project-scoped lookup fields would allow you to do that.

---

<div class="post-metadata">

**Author:** ![Phil\_Seeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/phil_seeman/32/81525_2.png) [@Phil\_Seeman](https://forum.asana.com/u/Phil_Seeman)\
**Post date:** [18 November 2026 02:32 UTC](https://forum.asana.com/t/project-scoped-lookup-fields/1161942/2 "2026-11-18T02:32:20Z")

</div>

@billyadams Is this getting at what you were aiming for in your other thread about automation scopes?

---

<div class="post-metadata">

**Author:** ![billyadams](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/billyadams/32/157936_2.png) [@billyadams](https://forum.asana.com/u/billyadams)\
**Post date:** [19 November 2026 16:18 UTC](https://forum.asana.com/t/project-scoped-lookup-fields/1161942/3 "2026-11-19T16:18:44Z")

</div>

No, unfortunately not. That other thread was more focused on the automation scope selections so you could establish a task → task trigger/action combination. And as I discovered, that was an issue with Help Center documentation, not with platform functionality.

I’m going to open a Product Feedback thread instead to have the Automations be able to scope a task → task.
