QA TOUCH + CLICKUP

Turn a failed test into a ClickUp task, in one step

Map a ClickUp workspace to each QA Touch project. From a test result, create a ClickUp task and a QA Touch issue together, or link tasks that already exist.

Setup: ClickUp app, workspace connection, project mapping

QA Touch records the failure. ClickUp holds the task.

Connect your ClickUp workspaces to QA Touch once, then map a workspace to each project. Testers can raise the work from the test result they are already looking at.

  • Problem: A failed test has to be re-created as a ClickUp task by hand.

    With the integration: Add Issue on a test result can create the ClickUp task and the QA Touch issue at the same time.

  • Problem: The task already exists in ClickUp, and a second one would be a duplicate.

    With the integration: Link existing ClickUp tasks to the test result instead of creating new ones.

  • Problem: Screenshots and files stay behind in the test result.

    With the integration: Attachments added in QA Touch appear on the ClickUp task.

Illustrative sample data. The page shows the idea of the hand-off, not the exact fields QA Touch sends.

What the integration does

Five capabilities from QA Touch’s ClickUp guide and blog post, from the first connection to a linked task.

Connect the workspaces you choose

Create a ClickUp app, enter its Client ID and Client Secret in QA Touch, then pick which workspaces QA Touch may access.

Administrator setup

Map a workspace to a project

Under Project Integration Mapping, select a ClickUp workspace for the QA Touch project and submit.

Per-project mapping

A task and an issue, together

From a test result, add a new ClickUp task and a QA Touch issue at the same time. Space, List and Status are required.

Assignees, tags and due date

Add several assignees and tags, and a due date. A tag created in the dropdown is also added to the ClickUp workspace.

Link tasks that already exist

From the action menu on a test result, view linked ClickUp tasks and tick existing ones to link them.

From ClickUp app to a task on your list

Step through the flow. The screens are schematic, drawn from the labels in the setup guide, not screenshots.

One-time ClickUp profile picture Settings ClickUp API

Create the app in ClickUp

Copy the redirect URL from QA Touch's ClickUp tab, then click Create New App in ClickUp, name it and paste the URL. ClickUp gives you a Client ID and a Client Secret.

QA Touch Administration Integration Settings ClickUp

Connect your workspaces

Enter the Client ID and Client Secret and click Generate Code & Map Workspaces. In the tab that opens, select the workspaces and click Connect Workspaces. Paste the access code back into QA Touch and submit.

QA Touch Projects Project Integration Mapping ClickUp

Map a workspace to the project

Open the ClickUp tab, select a ClickUp workspace and click Submit. Each QA Touch project is mapped on its own.

QA Touch Test run result Add Issue

Create the task and the issue together

Choose the option that adds a new ClickUp task and a QA Touch issue at the same time. Pick the Space, List and Status; assignees, tags and a due date are optional.

QA Touch Test result action icon ClickUp

Link tasks that already exist

Open the action icon on a test result and choose the ClickUp option. The linked tasks are listed, and you tick existing ones to link them.

Illustrative sample data. Workspace, task and tag names are examples.

What changes for your QA team

Testing stays in QA Touch. The work it creates lands where your team plans.

No double entry

The ClickUp task and the QA Touch issue are created in one step, so testers don’t log the same failure twice.

Evidence travels with the task

Attachments added in QA Touch show on the ClickUp task, and QA Touch posts a message in ClickUp when the task and issue are created.

Fewer duplicate tasks

When a task already exists, link it to the test result rather than creating another.

Set up once, map per project

An Administrator connects ClickUp once. After that, each project only needs a workspace mapping.

Who uses it, and for what

Choose a role to see a scenario the integration supports.

The team plans its work in ClickUp

Your developers already use ClickUp, and you want QA Touch connected before the next test cycle.

What they do

  1. Copy the redirect URL and create a ClickUp app.
  2. Enter the Client ID and Client Secret, choose the workspaces and submit the access code.
  3. Map a ClickUp workspace to each QA Touch project.

Result: the account is connected and each project has a workspace to create tasks in.

A checkout test fails

You are working through a test run and find a problem a developer needs to fix.

What they do

  1. Click Add Issue on the failed result and choose to add a ClickUp task and a QA Touch issue together.
  2. Pick the Space, List and Status, and add an assignee, tags or a due date if needed.
  3. Attach the evidence and submit.

Result: the task is in ClickUp with the attachments, and the issue is in QA Touch.

The task is already in ClickUp

A developer or product manager has already raised the problem, and the test result should point to it.

What they do

  1. Open the action icon on the test result.
  2. Choose the ClickUp option and review the linked tasks.
  3. Tick the existing tasks to link them.

Result: the result is linked to the tasks that already track the problem.

You work from ClickUp

You want QA findings in the same lists as the rest of your work.

What they do

  1. Open the List the tester chose in ClickUp.
  2. Find the task, its assignees, tags, due date and attachments.
  3. Work it like any other task.

Result: QA findings arrive in ClickUp without anyone copying them over.

Set it up in four parts

These steps follow QA Touch’s ClickUp integration guide: the redirect URL, the ClickUp app, the connection, then each project.

Before you start

  • A ClickUp account with the workspaces you want to connect.
  • A QA Touch Administrator login for Integration Settings.
  • The redirect URL from QA Touch, copied first.

Copy the redirect URL exactly as QA Touch shows it on the ClickUp tab. The guide and the blog post show it with different schemes (https and http), so use the one in your own account.

  1. Log in to QA Touch as an Administrator.
  2. Go to Administration → Integration Settings and open the ClickUp tab.
  3. Copy the redirect URL shown there.
  1. In ClickUp, click your profile picture and open Settings.
  2. Open ClickUp API and click Create New App.
  3. Name the app, for example QA Touch, and paste the redirect URL.
  4. Copy the Client ID and Client Secret ClickUp gives you.
  1. Back on the ClickUp tab in QA Touch, enter the Client ID and Client Secret.
  2. Click Generate Code & Map Workspaces. A new tab opens.
  3. Select the workspaces QA Touch may access and click Connect Workspaces.
  4. Copy the access code shown on the redirect page, paste it into QA Touch and click Submit.

connectedThe status shows connected when the configuration succeeds.

  1. Go to Projects → Project Integration Mapping and open the ClickUp tab.
  2. Select a ClickUp workspace and click Submit.
  3. On a test run result, use Add Issue to create a task, or the action icon to link existing ones.

Workspace mapped? See how a failed test becomes a task.

Questions about the ClickUp integration

Answers are based on QA Touch’s ClickUp integration guide and blog post.

What does the QA Touch ClickUp integration do?

It connects QA Touch to your ClickUp workspaces. Once a workspace is mapped to a project, testers can create a ClickUp task and a QA Touch issue at the same time from a test result, or link existing ClickUp tasks to it.

As an Administrator, copy the redirect URL from Administration → Integration Settings → ClickUp, create an app in ClickUp (Settings → ClickUp API → Create New App), then enter its Client ID and Client Secret in QA Touch and click Generate Code & Map Workspaces. Select the workspaces, copy the access code and submit it. The status shows connected.

ClickUp Space, List and Status are required. Assignees (more than one is allowed), tags (also more than one) and a due date are optional. A tag you create in the dropdown is also added to the ClickUp workspace.

Yes. On a test result, click the action icon and choose the ClickUp option. It lists the linked ClickUp tasks, and you tick existing tasks to link them.

Attachments added in QA Touch appear on the ClickUp task. The guide lists these file types: png, jpg, jpeg, gif, xls, xlsx, doc, docx, txt, pdf, csv, ppt, pptx, zip, mp4, webm and mov.

Go to Projects → Project Integration Mapping, open the ClickUp tab, select a ClickUp workspace and click Submit.

The guide and blog post describe tasks going from QA Touch to ClickUp, with QA Touch posting a message in ClickUp when a task and issue are created. They don’t describe changes syncing back, and they don’t describe the steps for unlinking a task.

Connect ClickUp to QA Touch

Connect once, map a workspace to your first QA Touch project, and create the next ClickUp task straight from a test result.