# Set portfolio fields when creating a project from a template

**URL:** <https://forum.asana.com/t/set-portfolio-fields-when-creating-a-project-from-a-template/1087890>\
**Category:** Product Ideas\
**Created:** [7 August 2025 21:01 UTC](https://forum.asana.com/t/set-portfolio-fields-when-creating-a-project-from-a-template/1087890 "2025-08-07T21:01:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [10 August 2025 18:35 UTC](https://forum.asana.com/t/set-portfolio-fields-when-creating-a-project-from-a-template/1087890/2 "2025-08-10T18:35:09Z")

</div>

@Nikki_Gilland,

Are you aware of this behavior, which may solve your problem:

> [@Custom Fields: Converting Task to Project](https://forum.asana.com/t/custom-fields-converting-task-to-project/812763/2):
>
> Welcome, @Lou_Wesely, If the custom fields in the project are in your org’s custom field library, and you specify a portfolio for the destination new project, and those custom fields also exist in that portfolio, then the project’s custom fields will take on the task’s custom field’s values. There’s no related facility other than the above; there’s no concept of any other behavior regarding the task’s custom fields. Thanks, Larry

And perhaps with rules you could verify that the custom fields needed are set before convert to project.

If this does help you, and you want to remove your #English Forum > Product Feedback request, please reply. Otherwise, this will remain open for others to vote on.

Thanks,

Larry

---

_[View the full topic](https://forum.asana.com/t/set-portfolio-fields-when-creating-a-project-from-a-template/1087890)._
