Skip to main content
Level 4
September 1, 2017
Question

How to get project form data to populate an issue custom form?

  • September 1, 2017
  • 13 replies
  • 1576 views
We currently accept project requests through our Request Queue. They come in as Issues, which we then convert to Projects. The data from the Issue custom form carries over into the Project custom form. However, when we want to create an issue associated with a project, the common form field data does not populate on the issue. Is there a way to make this happen? The Use Case: We create a master project to serve as the overview for a program. That master project has a wide variety of custom form fields to define the scope, deliverables, market, market sector, affect products, etc. We want to create issues for the separate deliverables, assign them to the relevant project managers, who will then convert those issues to projects. We don't want to manually enter the common, basic data that is already on the master project and that exists on the Issue form as well. Chris Watson KVH Industries, Inc.
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

13 replies

Level 4
January 18, 2018
All: I have a somewhat similar problem to solve. We have an Issue Type of Change Request. Currently, we have to manually type in any budget changes as it relates to the project (Business Case Budget, Baselined Budget, Planned Budget, etc.) into our Change Request Custom Form on the Issue because when it was set up years ago, I presume, there was no way to put any Project object details on an Issue. Is there anything related to how you resolved this posts issue that could assist with pulling those number from the Project to the Issue? Keep in mind these are all details that would exist post-project creation and so transferring from a request isn't possible. By the way, the goal of this is to minimize executive clicks. If a sponsor gets a CR, that custom form should have all the details they need to make a decision without clicking around the project to "hunt" for important financial detail (all of which we have calculated on a Project Custom Form already). I just can't find a way to get those calculated fields on the Project to appear on an Issue. Jason Maust McGuireWoods LLP
Level 10
September 5, 2017
This solution copies data during the conversion process using calculated fields. Please note that after the conversion, any changes to the master project data will not be reflected in the converted-to-projects. It's a "one-time" copy. Create an "Issue" custom form for "Project Data ISSUE Form" and create some custom calculated fields as follows: Field Label: Project Name; Calculation: Project.Name Create a "Project" custom form for "Project Data PROJECT Form" and add the existing calculated fields you just created above. The calculation you'll enter will be the field above in this format: {Project Name} On your master project, create the issues and attach the "Project Data ISSUE Form" form created above. Convert the issue to a project using a template that already has the "Project Data PROJECT Form" attached or attach the form during the conversion. Please let me know how this works out or if you have any problems! Narayan.D.Raum@SunTrust.com Narayan Raum Delivery Lead/System Administrator Workfront Center of Excellence SunTrust Bank
Level 8
September 4, 2017
I may be corrected, but I believe the inheritance is one way (issue converted to project, rather than project adding issue). Some alternatives: Copy the issue used to create the project into the newly created project Create multiple projects from the one issue, and use inter-project dependencies to link them Of the two, I'd suggest copying the issue. That way at least they all share the one project and project details. Barry Buchanan Work Management Australia