Skip to main content
New Participant
June 28, 2017
Archived

[CLOSED] - Integrate Custom forms across objects so we don't need to maintain multiple forms (request, project, tab)

  • June 28, 2017
  • 3 replies
  • 476 views

This post has been closed as a duplicate. All votes have been moved to the original: Custom Form Carry Over When Converting from Issue to Task/Project

Form 1: Request - I have a request process with a request custom form.

Form 2: Project - Since the request can be converted to a project, I have to have a project custom form to collect the request form data.

Form 3: Task - Since the request can be converted to a task, I have a task custom form to collect the request form data.

I can copy the initial form over, but then if I make updates to one form (add a new field) - I have to go back to every single form & and make the same update.

I'd like to be able to link the forms, especially when I have complicated logic built in.

3 replies

New Participant
February 6, 2019

The request-to-project needing identical copies of form is the same thing I grumble at as an admin.

New Participant
November 17, 2017

While I see the logic of not having a custom form from a request to a project to a task, this would only work if your custom form is meant to be the same in all 3 objects. I hope if Workfront would work on this feature that they don't take away the ability to allow separate custom forms for each object as they sometimes would take away functionality when implementing something new (eg copy and paste clipboard!). We have request custom forms that when converted to the projects, would use the same form with additional fields that we need only on projects.

New Participant
June 28, 2017

YESSSSSSSSSS!!!!!!!!!!!!!

We also need to capture the data on a form on a project > a request > to be converted to another project. hope that makes sense