How to create forms with branching logic on Asana

intermediate 8 min read Updated 2026-03-18

Quick Answer

Asana forms with branching logic use conditional fields that show or hide based on previous responses. You'll set up trigger fields with specific values, then configure dependent fields to appear only when certain conditions are met.

Try Asana Full Asana Review

Prerequisites

Active Asana account with form creation permissions
Access to a project where you want to add the form
Understanding of conditional logic concepts
Familiarity with Asana's custom fields feature

Step-by-Step Instructions

Create a new form in your project

Navigate to your project and click the Forms tab at the top. Click + Create form and give your form a descriptive name. Choose your form settings including who can submit and where tasks will be created.

Use a clear naming convention for forms with branching logic, like 'Support Request - Conditional'

Add your primary trigger field

Click + Add field and select Single-select dropdown or Multiple choice. This will be your trigger field that determines which additional fields appear. Add all the options that will control the branching logic, such as 'Bug Report', 'Feature Request', or 'General Question'.

Keep trigger options clear and mutually exclusive to avoid confusion in your branching logic

Create conditional fields for each branch

Add additional fields that should appear based on the trigger selection. For each field, click the gear icon next to the field name, then select Add condition. Choose your trigger field from the dropdown and specify which value should make this field visible.

Configure field dependencies

In the field settings, under Show this field when, select your trigger field and choose the specific option value. You can add multiple conditions using AND or OR logic. For example, show 'Bug Severity' only when 'Request Type' equals 'Bug Report'.

Test each condition as you create it to ensure the logic works as expected

Set up nested branching logic

Create additional layers of conditional fields by making some fields dependent on other conditional fields. Click + Add condition on dependent fields and select previously created conditional fields as triggers. This creates a cascading effect where Field C appears only when Field B is visible and has a specific value.

Keep nested logic simple - too many layers can confuse form users

Configure required field rules

For each conditional field, toggle the Required setting and choose whether it should be required Always or Only when visible. Select 'Only when visible' for conditional fields to prevent validation errors when the field is hidden.

Preview and test your form

Click Preview form to test all branching scenarios. Go through each possible path by selecting different trigger values and verifying that the correct fields appear and disappear. Check that required field validation works properly for all branches.

Test your form with colleagues before publishing to catch any logic issues

Publish and share your form

Once testing is complete, click Publish form to make it live. Copy the form URL from the Share button or embed it using the provided HTML code. Monitor form submissions to ensure the branching logic is working correctly for real users.

Include brief instructions at the top of your form explaining how the conditional fields work

Common Issues & Troubleshooting

Conditional fields are not appearing when expected

Check that your trigger field conditions are set correctly. Ensure the trigger value exactly matches what users select, including spelling and capitalization. Verify that the field dependency is set to the right trigger field.

Required field errors for hidden conditional fields

Edit each conditional field and change the required setting from Always to Only when visible. This prevents validation errors when the field is hidden based on branching logic.

Form becomes too complex with multiple branching paths

Simplify your form by reducing the number of conditional layers or splitting complex forms into multiple simpler forms. Consider using OR conditions instead of multiple nested AND conditions where possible.

Changes to branching logic not reflecting in live form

After making changes to conditional field settings, click Save and then Update form to push changes to the live version. Clear your browser cache and test again to see the updated logic.

Prices mentioned in this guide are pulled from current plan data and may change. Always verify on the official Asana website before purchasing.

Visit Asana View Asana Pricing