auto-populate a program for a project?

[AlvinaLa1]

We have a request form that includes a field dropdown that lists all active programs.

is it possible to have the dropdown selection from the request form then autopopulate the Project association's program?

[Madalyn_Destafney]

You probably could with Fusion, but instead, what is the use case for having a separate custom field with your programs vs. just using the native Program field (which already populates with active programs based on the portfolio selection - you won't see ALL in the dropdown on default it will only show 20 I think, but if you start typing the name of a program within the selected portfolio, it'll show to select. Upvote this Idea on increasing the number that shows on default!

[AlvinaLa1]

Thanks for the suggestion. We have two fields because one field in the request form indicates a related program when a user is making a request, and the other is the project's program that appears after a project is created (if I am understanding native correctly).

Are you suggesting we can put the project's native program field into a request form so it autopopulates? 

[Madalyn_Destafney]

Apologies, I read too quickly and didn't see it was for a request/issue form (where the native Program field is not available). When the issue is converted, it'll only be looking at the native Program field to determine its Program (which is based of course on the Programs within the Portfolio the converted request was brought into). The native, project-level Program field would only auto-populate based on a value of a custom form field (your program field) if you have Fusion (I'd imagine Fusion could do this but don't quote me on it), it wouldn't do this natively. 

[kautuk_sahni]

@AlvinaLa1 just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!