Field on request, project and task form isn't populating on task form

[Jared_Mauch]

I have the same multi-select dropdown field on request, project and task forms that only wants to populate the field on the project form when converting a request to a project using a project template. The project form is in the project details section and the task form is in the task details on the project template. I was hoping that the task field would auto-populate just like the field on the project form does, but I have to manually set the selection. Is it not possible to have the selection synced on the same filed in the three different forms?

[skyehansen]

If' I'm reading your post correctly, yes that's right. The fields would populate on task when you convert the request to a task, same as how they populate on the project when you convert the request to a project.

[Jared_Mauch]

Hi Skye,

I'm trying to have a task form on tasks already inside a project template be populated with the same fields that are also on the project form when converting the request to a project. The reason for the task form is so people who only have access to specific tasks can still view some of the fields from the project form without giving them access to the full project itself. I guess the field relationship for the fields on the request form can only be shared once with the project form and not handed off to a task form on the project template?

[skyehansen · Accepted solution]

the answers to the field get populated on the task at the point you convert the request to a task. If you are never going to convert the request to a task, then I suggest you replace your current custom form with a task custom form that has calculated fields to pull what you need from the project.

[Jared_Mauch]

Thanks for the clarification! I wasn't sure if a form with calculated fields to pull in from the project form was the only way or not. I'm working on the calculated fields for the form now.