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.
Would this request correspond to yours? If so, please vote for that, and reply here so I can merge.
Thanks,
Larry
@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.
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
1 Like
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)
1 Like
Agree 100% with the desire to bring project-level field info down into the tasks, this would make reporting a lot more powerful too
Of course it is one (along with Project Owner) in our Flowsana variables. 
1 Like
Of course it is 