# Lists

## Configuring Lists <a href="#configuring-forms" id="configuring-forms"></a>

Each ClickUp Form has two parts: ***when creating a ticket*** and ***when editing a ticket**.*

* Navigate to [Forms](https://web.clearfeed.app/objects/clickup) on the ClearFeed web console -> click on `Import from ClickUp`.
* You should see your Lists in the following format: Space Name > List Name

{% hint style="info" %}
**Supported ClickUp Field Types:** Status, Assignees, Due Date, Priority, Single-select, Text, Number, and Multi-select. We plan to add more ClickUp fields soon.
{% endhint %}

### *Create* Form <a href="#create-form" id="create-form"></a>

1. *Title* and *Description* are added to the Form by default. These are non-removable and pre-filled by ClearFeed. However, they can be hidden to prevent modification.
2. From the ClickUp Fields table (right-hand panel) - add the fields you want to be a part of the form.
3. Configure properties such as adding hint text, placeholder text, making fields optional, setting a default value, or hiding a field.
   * Learn more about field properties **here**.
   * Save your configuration.

<figure><img src="/files/11ylVBGJFMtXeSAjBIvo" alt=""><figcaption><p>Creating a ClickUp Form</p></figcaption></figure>

### *Edit* Form <a href="#edit-form" id="edit-form"></a>

If the Edit Form is enabled - users will see an Edit Ticket button when they create a ticket. You can provide requestors and responders the exclusive ability to modify fields after ticket creation.

Only the fields that are a part of the *Edit form* can be modified from the triage channel after a ticket is created.

1. Add fields from the `ClickUp Fields` table available on the right-hand side.
2. Configure properties such as making fields optional, setting a default value, or hiding a field.
   * Learn more about field properties [**here**](https://github.com/clearfeed/new-docs/blob/main/integrations/clickup/forms/README.md#field-properties).

{% hint style="success" %}
**Pro tip:** Use the **Add all Create Form fields** button to quickly add fields that are a part of the *Create* form to the *Edit* form.
{% endhint %}

## **Ticket Creation Without a Form** <a href="#allow-ticket-creation-without-a-form" id="allow-ticket-creation-without-a-form"></a>

* If all fields in a form are hidden, users can create tickets without completing the form.
* If all fields in a Form are set to be editable by *only responders*, requesters can create a ticket without filling out the form.
  * **Note**: Fields will have pre-filled or default values in both scenarios.

## Field Properties <a href="#field-properties" id="field-properties"></a>

* **Removing Fields:** Remove fields from a Form using the Delete icon.
  * **Note:** *Title* and *Description* are non-removable in the *Create Action* form. However, they can be hidden to prevent modification.
* **Reordering Fields:** To customize the order of the fields, click and hold a field in the left column, then drag and drop it to your desired position in the sequence.
  * **Note:** Non-removable fields will always be on top, while hidden fields will automatically move to the bottom once the changes are saved.
* **Non-responder Field Label:** Determines the field name displayed to the requestors when they use the form.
  * If fields are hidden - this property is not relevant.
* **Placeholder Text:** Text inside the field before users enter their information.
* **Hint Text:** The hint text is shown below the field to guide users on what to enter. Think of this as the field description.
* **Default Values:** Adds default values to the fields. Default values automatically populate the corresponding ClickUp fields when a ticket is created.
  * **Note**: Default values cannot be entered for non-removable fields.
* **Hidden Fields:** To ensure specific fields are not modified during ticket creation, you can hide them from the *Create Action* Form.
  * **Note**: When hiding a field, you must assign it a default value.
* **Permissions:** Specify who must fill out a field when creating or editing a ticket using the **Editable by** column. Choose between *All users* or only *Responders.*
  * **Note**: Users with the required field permission must fill it out when creating a ticket on Slack.
* **Required Field**: Specify if the field is optional or mandatory when creating or editing a ticket in the `Required field` column.

<figure><img src="/files/E6zzzvxFgJaAjjG6IDsi" alt=""><figcaption><p>Field properties for ClickUp</p></figcaption></figure>

## Mapping Forms to Collection <a href="#mapping-forms-to-collection" id="mapping-forms-to-collection"></a>

All active ClickUp Lists (forms) are available for ticket creation by default in Collections with ClickUp Ticketing enabled.

* You can limit the available Forms for ticket creation by mapping specific Forms to a Collection.

{% hint style="info" %}
Only Forms with an active [*Create Action*](#create-form) Form will be available for mapping.

* A form can be mapped to multiple collections.
  {% endhint %}

**How to map ClickUp Forms (Lists) to a Collection?**

1. Navigate to `Collections -> Settings`.
2. Go to `Ticketing Settings`.
3. In the Forms Availability section, select the `Specific Forms` option.
4. From the available Forms, select the ones you'd like to associate with this Collection.

<figure><img src="/files/M9hPsOm2A8tTjjOCL2T9" alt="" width="563"><figcaption><p>Mapping ClickUp forms to a Collection</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.clearfeed.ai/clearfeed-help-center/integrations/clickup/forms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.