Feature Requests

Ability to add logic inside of logic. For example: Being able to drill into different locations Country>State>City.

Currently, with forms, we can only dump answers as custom fields within a specific task. What we would like to achieve is that the questions and answers on the form could be directly transformed into tasks or subtasks, so that each relevant answer generates a separate action with the information provided by the user. For example: A customer onboarding process. The Project Manager completes an onboarding form with those mandatory data and those that they don't have and don't have are left blank. Each block or question on the form becomes a task or subtask. The user's response is included within that task/subtask as a context and those that are not covered later. So, instead of having all the information concentrated in custom fields for a single task, we could turn the form into an actionable list of work. And the questions or information that we don't have, with a Kant diagram we plan the rest of the information collection. The idea would be to move from a form model as a collection of information to a model where the form also serves to automatically generate an operational structure of work.

Use forms to update existing tasks fields. E.g in the inventory management template.. Use forms to CheckOut or CheckIn assets into the inventory using custom forms and update the value of stock in background.

Have the ability to export a form to a PDF/Doc to be able to use eslewhere

Create a system where our clients can create new support tickets for issues. Should be able to create a custom form and use a ticket number system. It would also be nice to have a guest view role for this.

Currently, the Task Name and Task Description fields retain the same field titles wherever they are referenced in form conditions. These default fields cannot be renamed for each occurrence. It would be beneficial to allow users to assign unique display names or labels to the Task Name and Task Description fields whenever they are used in conditions. This would improve clarity, especially in complex forms where the same field appears multiple times with different contexts or purposes.

On the ClickUp form, we can add a question description to fields, as shown in the screenshot, which allows us to provide a clearer explanation for certain questions that we ask. Currently, this is not available for fields that show up based on certain conditions. This would be extremely helpful to add a question description based on the condition.

Currently, it is possible to create Custom Fields that are assigned to specific Task Types. However, Forms do not allow: selecting a default Task Type for submitted tasks; displaying or using Custom Fields that belong to a specific Task Type. This creates an inconsistent experience because Task Type-specific fields can be configured in the workspace, but they become unusable when creating Forms. Current Behavior A Custom Field can be linked to a Task Type. When creating a Form: there is no option to assign a Task Type to the Form; Custom Fields associated with that Task Type are not available to add to the Form. As a result, it is impossible to create a Form that fully supports a specific Task Type. Expected Behavior Forms should support Task Types by allowing users to: select a default Task Type for all tasks created from the Form; automatically display Custom Fields associated with the selected Task Type; optionally filter the available fields based on the selected Task Type. This would make Forms consistent with the Task Type configuration available elsewhere in the product. Why This Matters Without Task Type support in Forms: Task Type-specific fields cannot be collected through Forms. Users cannot build Forms tailored to different workflows. Existing Task Type configuration loses its value in one of the primary task creation methods. Users are forced to rely on manual updates or automations after form submission, even though the Task Type is already known beforehand. Suggested Implementation When editing a Form: Add a Task Type selector in the Form settings. Once a Task Type is selected: automatically make its associated Custom Fields available in the Form builder; optionally pre-populate the Form with those fields. Every task created from the Form should automatically receive the selected Task Type. This would eliminate the current inconsistency and allow Forms to fully support Task Type-based workflows.

### Problem / Use Case: Currently, ClickUp Form logic only allows for showing or hiding an entire field. However, many workflows require the same field to be shown but with a restricted list of options based on a previous selection. Without this, we are forced to create multiple duplicate Custom Fields (e.g., "Version - Corolla," "Version - Tucson," etc.) to show the correct options, which clutters our Workspace, complicates reporting, and makes data mapping difficult. ### Requested Feature: (This is an alternative to Cascade Custom Field, at least for Forms) The ability to select which specific values of a Dropdown or Label field are visible when a specific condition is met in a Form. Example Scenario: I have two Custom Fields: * Field A (Car Model): Corolla, Tucson, X1 * Field B (Version): Basic, Complete, Premium Desired Logic: * If Corolla is selected Show Version field but only display options: Basic, Complete . * If Tucson is selected Show Version field and display all options: Basic, Complete, Premium . * If X1 is selected Show Version field but only display options: Complete, Premium . ### Benefits: Cleaner Data: Eliminates the need for redundant custom fields. User Experience: Prevents users from selecting invalid combinations (e.g., selecting a "Premium" version for a car model where that version doesn't exist). Efficiency: Simplifies Form setup and maintenance.