# Project variables **URL:** \ **Category:** Product Ideas\ **Created:** [17 March 2025 22:42 UTC](https://forum.asana.com/t/project-variables/1038512 "2025-03-17T22:42:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Herve\_Buisset](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/herve_buisset/32/287327_2.png) [@Herve\_Buisset](https://forum.asana.com/u/Herve_Buisset)\ **Post date:** [17 March 2025 22:42 UTC](https://forum.asana.com/t/project-variables/1038512/1 "2025-03-17T22:42:52Z")
Wouldn’t it be useful to have project variables? Variables that are assigned to a project instead of to a task, but can be used e.g to fill a task variable or to store info that is not related to one tasks, but some tasks. ---
**Author:** ![Larry\_Berger\_lpb](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/larry_berger_lpb/32/276017_2.png) [@Larry\_Berger\_lpb](https://forum.asana.com/u/Larry_Berger_lpb)\ **Post date:** [18 March 2025 01:44 UTC](https://forum.asana.com/t/project-variables/1038512/2 "2025-03-18T01:44:13Z")
@Herve_Buisset, Would this request correspond to yours? If so, please vote for that, and reply here so I can merge. > [@Project/system Variables for use in context](https://forum.asana.com/t/project-system-variables-for-use-in-context/40816): > > Would it be possible to add variables to the Asana Platform that could be used in context? For example: Create a variable \ that could be used in the following way where: Project\_Title: \ Task: Consult \ Task: Bid \ Task: Purchase \ would be interpreted like this: Project\_Title: Create Dashboard for Operations Task: Consult Create Dashboard for Operations Task: Bid Create Dashboard for Operations Task: Purchase Create… Thanks, Larry ---
**Author:** ![Herve\_Buisset](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/herve_buisset/32/287327_2.png) [@Herve\_Buisset](https://forum.asana.com/u/Herve_Buisset)\ **Post date:** [18 March 2025 09:30 UTC](https://forum.asana.com/t/project-variables/1038512/3 "2025-03-18T09:30:24Z")
@Larry_Berger_lpb Yes and no. As I understand the other thread these are more predefined variables, e.g. Project Title. I can see where this could be useful, my proposal is on a user lever, with all kind of variables (text, single select, …) that can be defined at a project level. Rules in a project would be able to read and change these variables, so they can be used at task level. ---
**Author:** ![Larry\_Berger\_lpb](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/larry_berger_lpb/32/276017_2.png) [@Larry\_Berger\_lpb](https://forum.asana.com/u/Larry_Berger_lpb)\ **Post date:** [18 March 2025 14:48 UTC](https://forum.asana.com/t/project-variables/1038512/4 "2025-03-18T14:48:47Z")
I’ve moved this topic to where you can click the title to scroll to the top and vote by clicking the Vote button, as I just did. It sounds like the variables would be portfolio-level custom fields (which apply to the project as a whole) to which you’d like to see functionality added, perhaps? Thanks, Larry ---
**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\ **Post date:** [18 March 2025 20:18 UTC](https://forum.asana.com/t/project-variables/1038512/5 "2025-03-18T20:18:26Z")
Yes this would be great. I would also like to see ‘Project name’ as a variable, too. And I agree leveraging a project’s custom fields into task-level rules would be useful. I voted, hope more do too (by clicking on the Vote button at the top left of this thread) ---
**Author:** ![Stephen\_Li](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/stephen_li/32/279555_2.png) [@Stephen\_Li](https://forum.asana.com/u/Stephen_Li)\ **Post date:** [18 March 2025 20:27 UTC](https://forum.asana.com/t/project-variables/1038512/6 "2025-03-18T20:27:40Z")
Agree 100% with the desire to bring project-level field info down into the tasks, this would make reporting a lot more powerful too ---
**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:** [19 March 2025 05:59 UTC](https://forum.asana.com/t/project-variables/1038512/7 "2025-03-19T05:59:47Z")
> [@Richard\_Sather](#): > > I would also like to see ‘Project name’ as a variable, Of course it is one (along with Project Owner) in our [Flowsana variables.](https://support.flowsana.net/help/variable-substitution-in-flowsana) 😉 ---
**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\ **Post date:** [19 March 2025 06:27 UTC](https://forum.asana.com/t/project-variables/1038512/8 "2025-03-19T06:27:25Z")
Of course it is 😜 ---
**Author:** ![anon47639439](https://luna1.co/8d76cd.png) [@anon47639439](https://forum.asana.com/u/anon47639439)\ **Post date:** [20 October 2025 12:14 UTC](https://forum.asana.com/t/project-variables/1038512/9 "2025-10-20T12:14:30Z")
This would be incredibly helpful for us too. We are using Asana, among others, to streamline customer success, and certain project-level variables (which could be defined as portfolio-level custom fields) need to be set in certain tasks and then trigger IF/THEN decision trees (e.g., if project is in X industry, then involve person Y or trigger sub-task Z)