> ## 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. # Asana Tasks > Connect Asana to create tasks from test results, file them automatically, and let Spur AI and the PR Agent read linked tasks. ## Overview Connect Asana to turn test results into Asana 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 you review a Test Plan run. * Have Spur create tasks automatically when a test finishes. * Reference an Asana task in Spur AI or in a pull request, so Spur can read it before it writes or runs tests. Spur sees only the projects that the Asana user who connects the integration can see. The connection applies to your current Application. ## Permissions Spur asks Asana for full permissions, because Asana has no narrower permission that lists project sections yet. Spur writes to Asana only to create a task and attach files to it. It never edits or deletes your existing tasks, projects, or settings. ## Connect Asana **1. Open the integrations page** Click the user profile button in the top right from any page, then click **Integrations**. Find the **Asana** card under **Issue Tracking** and click **Connect**. **2. Authorize Spur in Asana** Asana asks you to authorize Spur. Approve the request. Asana sends you back to the Spur integrations page. **3. Choose a workspace** If your authorization covers one workspace, Spur selects it for you. If it covers more than one, the card shows **Choose a workspace**. Click **Choose workspace**, pick one under **Workspace**, and click **Save Changes**. > [!NOTE] > > Spur sees every workspace that the connecting Asana account belongs to. Missing a workspace? Click **Reconnect Asana** in the settings dialog and sign in with an Asana account that belongs to it. ## Set your defaults Once connected, click **Settings** on the Asana card to open **Asana Integration Settings**. ### Workspace The **Workspace** dropdown appears when your authorization covers more than one workspace. Changing the workspace clears the default project and automatic filing. After you save a new workspace, the dialog stays open so you can pick a project in it. ### Default project Pick the **Default project** your team files bugs into. The default is **No default**, which means whoever creates a task picks the project each time. ### Automatic filing Turn on **Automatic filing** to have Spur create a task in the default project when a test finishes. Select **When a test fails**, **When a test passes**, or both. You need to pick a default project before you can turn this on. Automatically filed tasks use your field defaults. Spur attaches the failure video and screenshot when the run has them. If the description is longer than Asana allows, Spur shortens it. The full details stay on the Spur result. Automatic filing skips a task when the project requires a field that has no default, or a field that Spur cannot fill. The dialog names those fields so you can fix the setup. ### Field defaults After you pick a default project, **Field defaults** lists the values that every new task opens with: **Section**, **Assignee**, **Tags**, and the project's custom fields. **Section** appears when the project has sections. **Tags** appears when your workspace has tags. A star marks a field that Asana requires. You can change any default in the task form before you create a task. Automatic filing uses the defaults as saved. 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 **Asana** under **Create a Ticket**. The **New Asana Task** form opens. **2. Review what Spur filled in** Spur writes the title and description from the test result. The description includes the failure reason, reproduction steps, test execution details, and a link to the run. Edit either one before you create the task. **3. Set the task details** Under **Details**, set the following: * **Project**: the project to create the task in. This is required, and starts with your default project. * **Section**: the section to add the task to. Leave it on **Default** to use the project's first section. This field appears when the project has sections. * **Assignee**: a member of your workspace. Any custom fields the project requires also appear under **Details**, marked with a star. **4. Add optional fields** Under **Optional fields**, set **Tags**, **Start date**, and **Due date**. The project's optional custom fields appear here too. If you have not saved default tags, Spur selects a tag named "bug" when your workspace has one. Asana needs a due date when you set a start date. The start date must be before the due date. **5. Create the task** Click **Create Task**. Spur creates the task, links it to the test, and shows a confirmation with an **Open in Asana** link. > [!TIP] > > When you connect another issue tracker, the form header shows a **Switch to** button for it. With two or more other trackers connected, the header shows a **Switch tracker** menu instead. Switching keeps the title and description you have already edited. ### Supported custom fields Spur can fill these Asana custom field types: single-select, multi-select, text, number, date, and people. It cannot fill other field types, formula fields, or read-only fields. If a project requires a field that Spur cannot fill, the form names that field. You cannot create a task in that project. ## Create a task from Test Plan Review You can create Asana tasks without leaving [Test Plan Review](https://docs.spurtest.com/analysing-tests/test-plan-review.md). Mark a result as a bug, then select **Create Asana 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 Asana tasks in Spur AI With Asana 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.asana.com/1//project//task/`. Older links in the form `https://app.asana.com/0//` work too. Spur AI reads the title, description, custom fields, status, assignee, tags, parent task and subtasks, comments, and images uploaded to the task. Use it to write tests from a task. ## Read Asana tasks in the PR Agent The [PR Agent](https://docs.spurtest.com/running-tests/cicd/pr-agent.md) reads Asana 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). ## View and sync linked tasks A task you create appears in the test's share panel. Asana tasks have no short key, so Spur shows the task's title. The status pill shows the task's section, or **Completed** when the task is done. Click **Sync** to pull the latest title, status, and assignee from Asana. ## Troubleshooting | What you see | What to do | | - | - | | Asana rejected the saved connection | The authorization was revoked or expired. Click **Reconnect** on the Asana card, or **Reconnect Asana** in the settings dialog. | | Choose a workspace to finish setup | Your authorization covers more than one workspace. Pick one under **Workspace** and click **Save Changes**. | | Asana projects, fields, or data failed to load | Click **Retry**. If a project is still missing, check that the Asana user who connected can see it. | | This project requires fields Spur can't set yet | The project requires a custom field that Spur cannot fill. Pick another project, or [contact the Spur team](https://docs.spurtest.com/additional-resources/contact-us.md) with the field name. | | Add a due date to set a start date | Set a **Due date**, or clear the **Start date**. | | The description is too long for Asana | Shorten the description, then click **Create Task** again. | | Asana rate limit reached | Asana is limiting requests. Wait a moment, then try again. | | Created the Asana task, but Spur could not link it | The task exists in Asana. 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 Asana card and click **Disconnect**, then confirm. Spur stops creating and reading tasks, and clears the default project and automatic filing. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.