Feature Requests

Please search first before posting to help others find and vote for your idea!
Ability for Forms to link to "Parent Task" and "Pre-Set" Permissions - Form Privacy Features
I would like to have forms link back to the person assigned the form response - currently, the only way to ENSURE someone completes a form is by assigning them a task called "complete form" (otherwise, people forget to provide feedback via form). But the problem is that when they complete this form, it creates another task... kinda useless for our experience. For any HR department wanting to use forms for "Monthly Feedback" on their work experience, this becomes a burden because while automations can link them back to one another, that's a lot of automations for an entire organization (1 automation per person). Super Agents help with linking, but the problem is that Super Agents can NOT set permissions... so even if I set the permissions on the reminder tasks, the form response permissions do not carry over even if the link was clicked directly from a task description, and that creates a problem of everyone being able to see people's responses on their Monthly reflections unless I manually set those permissions. So the problem is two-fold: we need the ability to set permissions via automations or Super Agents. We also need the ability for forms to link to their parent tasks or set the permissions before the response. I'd imagine many people have used feedback forms, but if you want that feedback to be private and hidden from the masses, there is currently no way (other than manual intervention) to automatically prevent exposure of private responses.
0
·
Forms
Conditional Logic: Ability to filter/limit dropdown and label options based on previous selections
### 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.
1
·
Forms
Load More