Custom Fields: Converting Task to Project

[Lou_Wesely]

Greetings All,

I have a similar question as the below thread from 2023. I have custom fields added to a task which I am converting to a project using a template that contains the same custom fields from the library.

Once the task is converted, the data that was in those custom fields does not carry over. This works fine at the Portfolio level, just need to figure out how to make it work at the Project level.

Any ideas how to make this work if it’s an available feature?

Thanks

Continuing the discussion from Converting a Task to a Project – can I also move custom fields from the original task to custom fields in a task in the new project?:

[lpb]

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