Beginner question: Turning custom fields into project tasks | Community
Skip to main content
M
MattLe3
New Participant
June 28, 2024
Solved

Beginner question: Turning custom fields into project tasks

  • June 28, 2024
  • 1 reply
  • 462 views

Hi - sorry if this has been done to death, but I can't find the answer going through this site the last couple days.

 

I want to allow end users to select multiple assets on a custom form. I have it built using yes/no checkboxes a section of custom fields. I can see the answers in the request issue. And when I convert to project I see their selections in the project details. Yet... what I'd really like is for those selections to become tasks in the project on conversion. What am I missing? Or is this a Fusion thing? 

 

Thanks

 

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 VicSellers

Hi @mattle3 - This would require Fusion. The typical setup here is that you would have a core project template with all the tasks possible. So, when a request is submitted, you could have Fusion remove the tasks that aren't needed (the deliverables that weren't selected). Opinions may vary, but I think deleting is easier than adding in this case. This is a high-level explanation, it's more in the weeds when you get to setup, but hope that helps as a starting point!

1 reply

VicSellers
VicSellersAccepted solution
New Participant
June 28, 2024

Hi @mattle3 - This would require Fusion. The typical setup here is that you would have a core project template with all the tasks possible. So, when a request is submitted, you could have Fusion remove the tasks that aren't needed (the deliverables that weren't selected). Opinions may vary, but I think deleting is easier than adding in this case. This is a high-level explanation, it's more in the weeds when you get to setup, but hope that helps as a starting point!

    Terms & ConditionsAccessibility statement

    Loading footer...