Feature Requests

It would be awesome if we could hide custom field values (i.e., dropdowns) when it is no longer publicly needed, but we want to retain the original submissions with those values. Example: removing event registration options when they are full - without losing which event they registered for data.

It is puzzling that there is no limit on uploading photos in the "Tasks" section, yet the form itself allows only 15 fields in total. I believe the photo attachment capability needs to be expanded, especially since the data ultimately feeds into the task list anyway.

It would be incredibly helpful if form fields in ClickUp could populate the task description directly without creating new custom fields in the associated list. This feature would allow users to collect detailed information via forms and store it in the task description, keeping the list structure clean and avoiding unnecessary custom fields. This functionality would be particularly useful for teams that rely heavily on forms for task creation but do not need all form data to be stored as custom fields. It would streamline workflows and improve task organization. Thank you for considering this feature!

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.

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.

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.

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.

It would be nice if there was a way that ClickUp could detect who submitted a form and then add it to a people custom field. I know that this is possible with the Account Authenticated Forms setting, but this setting is for the entire workspace and we have forms that need to be open to the public/people outside of our workspace. Maybe this means making the Account Authenticated Forms available on a per form basis instead of the entire workspace.

Even your own Clickup Brain thinks this is a downgrade in this chat below. Me: I used to be able to map the fields in the forms. This seems to be missing PonderingBrain: Yeah, you're not imagining things. The ability to directly map a custom field response to the task name within the form builder isn't how it works anymore. The current setup only lets you add "Task Name" as its own standalone question on the form (so the submitter types the name manually), but there's no option to say "use this other field as the task name." The official workaround ClickUp recommends now is the Automation route: Go to your Email list → Automations Trigger: Task created → set "Created by" to Forms only Action: Change task name → insert the dynamic value for your Newsletter Subject custom field That'll auto-rename every form submission the instant it lands. It's a one-time setup and takes like 30 seconds. Want me to walk you through it more, or are you good from here? Me: Dislike That's really awful PonderingBrain: Honestly, yeah. It's a downgrade. Having to build a separate automation for something that used to be a simple field mapping is annoying. Especially when you've already got the data right there on the form. On the bright side, the automation is permanent once it's set up and you'll never think about it again. But I hear you, it shouldn't require that extra step.

Hi there, Im building a feedback form and I see the five star option for rating. Could we also get a NPS Score rating. It is a common rating tool Im amazed its not there already!