Portfolio selection at issue/request level that will populate the Portfolio field on the project? | Community
Skip to main content
amybillmayer
amybillmayer
Level 4
April 17, 2024
Solved

Portfolio selection at issue/request level that will populate the Portfolio field on the project?

  • April 17, 2024
  • 1 reply
  • 942 views

Hi all - I'm trying to find a way to have the Portfolio field on a project automatically populate based on a field (Portfolio, typeahead) from the issue/request.

 

Currently, we have requesters choosing the Portfolio, then at project conversion, our planners are manually populating the Portfolio field based on the selection from the request.

 

Seems like we should be able to carry that over somehow, but I can't figure it out!! Has anyone done this before?

 

Thank you in advance ...

Best answer by Richard__Carlson

You can use templates to convert issues to project, in the templates you have the ability to define specific portfolios and programs

1 reply

Richard__Carlson
Community Advisor
Richard__CarlsonCommunity AdvisorAccepted solution
Community Advisor
April 17, 2024

You can use templates to convert issues to project, in the templates you have the ability to define specific portfolios and programs

amybillmayer
amybillmayerAuthor
Level 4
May 9, 2024

Thank you for the reply, but we have a "many template" to "many portfolio" ratio - no one template applies to any one portfolio.

Richard__Carlson
Community Advisor
Richard__CarlsonCommunity Advisor
Community Advisor
May 9, 2024

After rereading your original question it might be something to do with your custom forms.  If you are capturing information on a request (issue) custom form when you convert it to the project there needs to be a corresponding project version of the custom form.  If your issue and project custom forms are the same the data will map correctly from request to project.

Terms & ConditionsAccessibility statement

Loading footer...