Feature Requests

Please search first before posting to help others find and vote for your idea!
Restrict Task Types by List and Location
Currently, when we create a task type, it becomes available across the entire workspace. This creates issues for standardization, as we want to enforce the use of specific task types within certain lists and even based on location. We’d like the ability to restrict task types to a list or location, so team members only see the relevant options. For example, in some cases, we only want three task types available within a given list. This functionality will help us: *Enforce consistency in how tasks are categorized. *Limit confusion by only presenting relevant task types. *Better leverage the beta functionality of fields tied to task types. IMPACT: Without this, team members can select incorrect task types, leading to data inconsistency and reduced effectiveness of field-based reporting and automation. REQUEST: *Ability to configure which task types are available per list, space, and/or entire workspace. Include the ability to manage ClickUp-created task types, such as Task, Milestone, Meeting Note, Key Result, Person, etc.) --By Location (Department/Team/Region): For example, the Sales – Europe list may only need three task types (“Lead,” “Demo Scheduled,” and “Contract Sent”), while Sales – US might require a different set. Restricting by location would keep task types relevant for each group. --Space: If an organization manages multiple workspaces (e.g., Operations vs. IT), admins could enforce different task type sets per workspace. This would prevent irrelevant task types from appearing in the wrong context (e.g., IT-specific types showing up in Sales). --Workspace: We may want to make certain task lists available across the workspace still. *Add to the space configuration/creation to set the task types available for each, in case there are no task types available at the workspace level.
22
·
Task types
·
building now
Add “Task Type” as a configurable field in the Fillout → ClickUp integration
We use the Fillout → ClickUp integration to automatically create ClickUp tasks from form submissions. We recently redesigned our ClickUp workflow to use different Task Types, with each Task Type having its own set of Custom Fields. We need Fillout to populate those Custom Fields when the task is created. The issue is that the Fillout integration currently creates every task using the default Task Type. Because of this, only the Custom Fields associated with the default Task Type are available at the moment of creation. If we change the Task Type afterward using a ClickUp Automation or apply a Task Template, the correct Custom Fields can be added to the task, but Fillout cannot populate them retroactively because those fields did not exist when the task was originally created. We tested several workarounds, including: Changing the Task Type through a ClickUp Automation. Using a Text Custom Field from Fillout as a trigger. Applying a Task Template through an Automation. Using the Task Type associated with the Template. These approaches can change the Task Type and/or add the Custom Fields afterward, but they cannot solve the core issue because Fillout can only populate Custom Fields that already exist when the task is created. ##### Requested feature We would like Task Type to be available as a configurable/mappable field in the Fillout → ClickUp integration. Ideally, the workflow would be: Fillout submission → determine Task Type → create ClickUp task with that Task Type → populate the Custom Fields associated with that Task Type For example, if a Fillout submission indicates that the task should be “Bug,” the integration would create the task as the “Bug” Task Type from the beginning. This would make all of the Custom Fields associated with that Task Type available before Fillout attempts to populate them. This functionality would allow users to build more advanced workflows where different form submissions create different ClickUp Task Types, each with their own Custom Fields. At the moment, there does not appear to be a native workaround for this use case because changing the Task Type or adding the Custom Fields after task creation happens too late for the Fillout integration to populate them. Please consider adding Task Type as a supported field in the Fillout → ClickUp integration.
0
·
Task types
Load More
→