Is it possible to nest a custom task field on a project level form? | Community
Skip to main content
O
OmahaOmaha
Level 4
November 12, 2024
Solved

Is it possible to nest a custom task field on a project level form?

  • November 12, 2024
  • 1 reply
  • 511 views

We're creating some custom task level fields that we want to nest on a project level form.  Is this possible or would it be best to attempt to nest this task level fields on a parent task?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by monicacardoso

Hi @omahaomaha, 

 

Thank you for your question! Currently, custom fields in Workfront are tied to specific object types. If you are trying to use task-level custom fields on a project-level custom form, this is not natively supported. 

 

You could select both the project and task object when creating your custom form, but those fields would only exist within their respective objects and could not interact with each other. The options here would be: 

 

  1. The solution you mentioned. If you want task-level custom fields to be grouped logically, create a parent task within the project → add the task-level custom form with the desired fields to that parent task. 
  2. If the primary goal is to display task-level custom field data in the context of the project, you could create a task report → include filters to show only tasks for a specific project or parent task → add the task-level custom fields as columns in the report → add the report to a project dashboard or embed it in the project layout. 

 

- Monica 

1 reply

M
Adobe Employee
monicacardosoAdobe EmployeeAccepted solution
Adobe Employee
November 19, 2024

Hi @omahaomaha, 

 

Thank you for your question! Currently, custom fields in Workfront are tied to specific object types. If you are trying to use task-level custom fields on a project-level custom form, this is not natively supported. 

 

You could select both the project and task object when creating your custom form, but those fields would only exist within their respective objects and could not interact with each other. The options here would be: 

 

  1. The solution you mentioned. If you want task-level custom fields to be grouped logically, create a parent task within the project → add the task-level custom form with the desired fields to that parent task. 
  2. If the primary goal is to display task-level custom field data in the context of the project, you could create a task report → include filters to show only tasks for a specific project or parent task → add the task-level custom fields as columns in the report → add the report to a project dashboard or embed it in the project layout. 

 

- Monica 

Terms & ConditionsAccessibility statement

Loading footer...