Ability to pull from project and task blueprints from same request form

We have an incoming project request form where X is selected as the answer for a question, a task is created from a blueprint, but if Y is selected, the request should pull from our project blueprints. Request that selects X is a smaller request that doesn't require formal routing. Requests that select Y are larger requests that must go through our formal routing process.

We really don't want to have to create another request form because we already have quite the list of request forms.

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Cansu Yetisgin

Hello @Ashley Fischer, thank you so much for the feedback and posting your use case here, it's been shared with our Product team 😊

Judy Feldmeier

Hi there! Upvoting this as well. In many cases, we want the flexibility to kick off a project in some instances and just a task in others, depending on the complexity of the request, but the current setup doesn’t support this. Would love to see this implemented!

Pace McCulloch

FYI this is possible now with question routing, use follow up actions to add tasks based on answers or send them to another page.

Megan Albrecht (Bethke)

We have many different instances where we need this! For example, in marketing, some requests may be a small ask, and others may be a large, robust project with multiple moving parts. It would be great to have them all in the list of "marketing requests", and have some as a simple task, others as a project with multiple tasks, so that all marketing needs are accounted for. This is applicable to many of our other departments needs as well, this is just one of many different examples.

Basudha Sakshyarika

Hello @Megan Albrecht (Bethke), thank you so much for the feedback and posting your use case here. I have forwarded it to our Product team 😊