We need IF/Then logic so the forms can be more dynamic. For example, we may want to hide 5 questions unless the user selects a specific item. This could be a check box, multi-select, or dropdown result. Basically something like:
IF Dropdown-X = “shoot” THEN show shoot/event panel
or if you aren’t going to employ panels or sections, then it could just be multiple IF/Then statements like:
IF Dropdown-X = “shoot” THEN show Q10
IF Dropdown-X = “shoot” THEN show Q11
IF Dropdown-X = “shoot” THEN show Q12
IF Dropdown-X = “shoot” THEN show Q13
Allow form branching/ skip/hide question like that which is available in Wufoo and MS Forms to Asana Forms.
I want our form submitters to see questions on the form specific to their responses to previous questions. They should be able to jump from one question to another in a form according to the responses to specific questions.
I am loving the new automation rules on projects and wondered if this is soon going to be extended to forms? Ideally we would like to be able to design forms that are responsive to user input e.g. if a specific option is selected from a drop down in a form than additional information is requested.
Hi @Clare_Stone Thank you for sharing your feedback with us!
There is an existing thread in the Forum regarding this topic so I’m merging your post with this main thread to avoid duplications and consolidate votes. I hope it’s OK
Thanks Natalia, happy to have this all consolidated
Do we have any indication on whether or not this is on Asana’s road map? Would just like to inform our planning on whether we can use Asana in this way any time soon or do we need to find an alternative. Preferably we could just stick with Asana
Hi Natalia - wondering if there’s been an update to this request for automating forms logic/making form fields conditional. I am encouraging my entire org to use one form as a ticket/request mechanism. B2B and B2C divisions have 70% common requirements but the last 30 % are custom to both. I would ideally like to show the specific fields on selection of some previous fields, but right now don’t see that supported on Asana. The alternative is to show all fields but it really makes the form ugly and unworkable. Please suggest
I’d like to see this as well. Supposedly it’s available to Business customers per the help page for forms (Create Forms in Asana | Product Guide • Asana Product Guide) but the documentation for branching logic is incomplete and I’ve not been able to locate the feature in my account even though I have Business.
Hi @Josh_Couch, welcome to the community forum and thanks for reporting this! We have some upcoming updates for Forms but these features are not available yet. Apologies for any confusion! We’ll make sure to keep this thread updated as soon as we have more information!
I’m excited to announce we’ve started rolling out Forms Branching!
With this new feature, you can associate follow-up questions to drop-down or multi-select answers. For example, if a user selects a specific answer in the drop-down, they automatically receive a follow up question related to that answer. You can also create more follow up questions for those answers, it’s be possible to have up to 5 branches per question.
Please find more details and screenshots in our recent announcement here:
We’re rolling out this update gradually, so don’t worry if you can’t access this feature just yet, it will be available to everyone within the next couple of days/weeks!
Let me know if you have any questions or feedback!
EDIT: I am incorrect. Thanks to @Richard_Sather and @lpb point out below, you can indeed include a field more than once in a form. Thanks guys.
In this form below, I want to have the “Platform’ field selectable if they choose Bug or New Feature, but not if they choose Inquiry. Since the field can only exist once in the form its not possible to add it to both branches.
Hi @Justin_Roberts , I’ve merged your post into this existing one.
In your case however, you can actually use the field twice under both branches. You will get a warning, which is fine since the field is connected to two different branches.
I think that’s not the case. You see a warning, and that warning is in red, but I just created a form with a question with two branches and the same custom field in each just by going ahead and selecting the field that’s “Already in use”:
Thank you for sharing your feedback with us!
