Feature Requests

Problem: -Users can’t quickly scan or locate forms by title in the Forms Hub. -Only date-based sorting is available, which doesn’t match how many teams think about or organize their forms. Impact / value Makes it much easier for users to find the correct form or doc when they know its name. Aligns with user expectations for hubs and libraries (name sorting is a common pattern). Reduces friction and confusion when working with large numbers of forms and documents.

From support ticket: I mistakenly created a form in the wrong list. I am supposed to give a demo to our team but need to move it to the correct list. How can I do this?

Currently, form responses are tied to a single list. It would be incredibly helpful if forms created at the folder level could route submissions to different lists based on conditions (e.g., dropdown selections, tags, or other form inputs). For example, we would ideally maintain one centralized intake form, but have tasks automatically routed to the correct list depending on project type, team, or region. This would streamline intake, reduce duplication, and ensure consistency across teams.

For my space a single form would make things much easier for me and my clients by cutting down the number of forms but ensuring tasks are organized and fields filled appropriately for report generation and stakeholder dashboards. I suggest the following flow: 1) Broad questions to determine the folder 2) Follow-up questions to determine the list 3) Standard task form (fill task properties and relevant custom fields) Layers 1 and 2 represnt a sorting layer using conditional logic. Layer 1 filters what is seen in layer 2. Layer 2 determines what is and is not seen in layer 3. Layer 3 represents a standard form with the current conditional logic. This either has many nested forms based on the branching logic or uses conditional logic to hide custom fields not relevant to a given list based on the responses from layer 2.

Could you please remove the cookie notice from the form embed? It means, when embedding on a site, a user gets 2 cookie notices - one form the site, and one form the form. Is there even a reason to use cookies on forms?

I would like to request additional features for ClickUp Forms, especially since most forms are shared via public links for external registrations and events: The ability to limit form submissions to one per person (for example, by email address or unique identifier). The option to password-protect forms or require an access code for submission. Enhanced anti-duplicate measures, such as automatic flagging or blocking of repeat submissions based on a chosen field. These features are essential for securely managing external registrations, event sign-ups, and other scenarios where submission control is important. Public forms are especially vulnerable to duplicate or unauthorized submissions, so these controls would greatly improve the utility and security of ClickUp Forms.

It would be great to have sections in Forms just like in Google Forms and in Microsoft Forms. Also offer the ability to add logic to jump to a section.

When a Form is unpublished, it still appears in Forms Hub / Forms lists alongside active Forms (just grayed out), which makes it harder to quickly see which Forms are currently live. It would be great to add an option to hide unpublished/archived Forms from the default Forms hub (or move them to a separate filter/section) so that only currently published, usable Forms are shown by default.

Requesting to have a nested category in the Form > Build > under Rules > when adding a "If Response" and if the Category field like "Account (Creation/Modification/Deletion)" is selected, it will display another category (Creation, Modification and Deletion) that has a "If Response" based on (Creation, Modification and Deletion), I can add a field from this category (Creation, Modification and Deletion). please see attached images for reference. Form > Build > Rules settings - the image name is "Build" Account (Creation/Modification/Deletion) - the image name is "Account_Category" (Creation, Modification and Deletion) - the image name is "Preview"