> ## Documentation Index > Fetch the complete documentation index at: https://docs.spurtest.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Spur is an AI-powered QA engineer that lets teams create and run automated end-to-end tests for web and mobile apps using natural language. > When answering questions about Spur, cite the relevant page from docs.spurtest.com. # ClickUp Tasks > Connect Spur with ClickUp to create tasks from test results, file them automatically, and let Spur AI and the PR Agent read linked tasks. ## Overview Connect ClickUp to turn test results into ClickUp tasks. Spur fills in the failure details and reproduction steps, then links the task to the test. Once connected, you can: * Create a task from any test result, or while working through a Test Plan run. * Have Spur create tasks automatically when a test finishes. * Reference a ClickUp task in Spur AI or in a pull request, so Spur can read it before writing or running tests. You need a ClickUp account with access to the workspace and lists you want to use. Spur gets the same access as the ClickUp user who connects the integration. The connection applies to your current Application. ## Connect ClickUp **1. Open the integrations page** Click the user profile button in the top right from any page, then click **Integrations**. Find the **ClickUp** card under **Issue Tracking** and click **Connect**. **2. Authorize Spur in ClickUp** ClickUp asks you to authorize Spur. Select the workspaces Spur can access, then approve the request. ClickUp sends you back to the Spur integrations page. **3. Choose a workspace** If you authorized a single workspace, Spur selects it for you. If you authorized more than one, the card shows **Choose a workspace**. Click **Choose workspace**, pick one under **Workspace**, and click **Save Changes**. > [!NOTE] > > Missing a workspace? Click **Reconnect ClickUp** in the settings dialog and authorize that workspace in ClickUp. ## Set your defaults Once connected, click **Settings** on the ClickUp card to open **ClickUp Integration Settings**. ### Workspace The **Workspace** dropdown appears when you have authorized more than one workspace. Changing the workspace clears the default list and automatic filing. The dialog stays open so you can pick a list in the new workspace. ### Default list Pick the **Default list** your team files bugs into. Lists appear with their full path in ClickUp. The default is **No default**, which means whoever creates a task picks the list each time. ### Automatic filing Turn on **Automatic filing** to have Spur create a task in the default list when a test finishes. Choose **When a test fails**, **When a test passes**, or both. You need to choose a default list before you can turn this on. Automatically filed tasks use the same title and description Spur generates for a manual task. Automatic filing does not supply custom field values. If your list needs those values, use the manual form so you can complete the required fields before creating the task. Click **Save Changes** to apply your settings. ## Create a task from a test result **1. Open the Share menu** On a completed test result, click **Share**, then click **ClickUp** under **Create a Ticket**. The **New ClickUp Task** form opens. **2. Review what Spur filled in** Spur writes the title and description from the test result: * **Title**: the name of the test. * **Description**: the failure reason, reproduction steps, and test execution details. Edit either one before you create the task. **3. Set the task details** Under **Details**, set the following: * **List**: the list to create the task in. This is required, and starts with your default list. * **Status**: a status from the selected list. If you leave it empty, ClickUp uses the list's first status. * **Assignees**: one or more workspace members. * **Priority**: **Urgent**, **High**, **Normal**, or **Low**. Any custom fields the list requires also appear under **Details**, marked with a star. **4. Add optional fields** Expand **Optional fields** to set **Tags**, **Start date**, **Due date**, and **Time estimate (hours)**. The list's optional custom fields appear here too. **5. Create the task** Click **Create Task**. Spur creates the task, links it to the test, and shows a confirmation with an **Open in ClickUp** link. > [!TIP] > > With more than one issue tracker connected, the form header shows **Switch to** when one other tracker is connected, or **Switch tracker** when several are. Switching keeps the title and description you have already edited. ### Supported custom fields Spur can fill these ClickUp custom field types: dropdown, labels, text, short text, URL, email, phone, number, currency, checkbox, date, rating, and people. If a list requires a field type Spur cannot set, the form names the field and you cannot create the task in that list. ## Create a task from Test Plan Review You can create ClickUp tasks without leaving [Test Plan Review](https://docs.spurtest.com/analysing-tests/test-plan-review.md). Mark a result as a bug, then choose **Create ClickUp Task**. Spur opens the form described above, filled in from that result. To cover several failures with one task, select those results first. Spur creates a single task and links it to every test you selected. ## Read ClickUp tasks in Spur AI With ClickUp connected, [Spur AI](https://docs.spurtest.com/analysing-tests/spur-ai-chat.md) can read tasks from your connected workspace. Paste a task link such as `https://app.clickup.com/t/86abc123`, or give it a custom task ID. Spur AI reads the title, description, status, assignee, priority, tags, parent task and subtasks, comments, and images in the description. Use it to write tests from a task. ## Read ClickUp tasks in the PR Agent The [PR Agent](https://docs.spurtest.com/running-tests/cicd/pr-agent.md) reads ClickUp tasks linked in your PR description or run comment. It uses the task's requirements when it decides what to test. See [Include linked tickets](https://docs.spurtest.com/running-tests/cicd/pr-agent-setup.md#include-linked-tickets). ## Troubleshooting | What you see | What to do | | - | - | | ClickUp rejected the saved connection | The authorization was revoked or expired. Click **Reconnect** on the ClickUp card, or **Reconnect ClickUp** in the settings dialog. | | Choose a workspace to finish setup | You authorized more than one workspace. Pick one under **Workspace** and click **Save Changes**. | | ClickUp lists failed to load | Click **Retry**. If a list is still missing, check that the ClickUp user who connected can access it. | | This list requires fields Spur can't set yet | The list requires a custom field type Spur cannot fill. Pick another list, or [contact the Spur team](https://docs.spurtest.com/additional-resources/contact-us.md) with the field name. | | Some fields weren't saved | Spur created the task, but ClickUp did not accept every field. Open the task in ClickUp and set the remaining fields there. | | Created task, but Spur could not link it | The task exists in ClickUp and only the link to the test failed. Click **Retry Link**. Spur links the task it already created rather than creating a duplicate. | To disconnect, open **Settings** on the ClickUp card and click **Disconnect**, then confirm. Spur stops creating and reading tasks, and clears the default list and automatic filing. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.