Where results land

ClickUp integration

TesterArmy turns the issues the agents find into ClickUp tasks through one connection shared by the whole project.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Task

What the task carries

Each ClickUp task includes the issue's description, expected versus actual behavior, reproduction steps, a priority mapped from severity, a screenshot link and a link back to the TesterArmy issue.

ClickUp · Bugs

Discount code is not applied at checkoutSeverity 5Bugs

Priority: Urgent
Description: The code field accepts the value but the order total does not change.
Expected vs actual: The total should drop by the discount but stays at the full price.
Reproduction steps: Sign in, add an item, open checkout, enter the code, press Apply.
Screenshot: View screenshot
TesterArmy issue: Open in TesterArmy

One connection
One teammate connects a ClickUp Workspace and the connection is shared by the whole project.
Adjust before creating
Title, Space, List, status, priority, assignee and due date can be changed in the dialog before creating.
No duplicate tasks
Each issue links to at most one ClickUp task, and exporting again opens that task instead.

[02] Setup

How it works

Setup is one ClickUp sign-in from the project's Integrations settings. ClickUp has no app identity for such connections, so TesterArmy creates tasks through the account that connected ClickUp.

Open the ClickUp integration

In Project Settings, open Integrations, choose ClickUp and click Connect ClickUp.

Approve TesterArmy in ClickUp

Approve TesterArmy for a ClickUp Workspace on the consent screen; ClickUp OAuth has no permission scopes to pick.

Pick the default List

Back in TesterArmy, pick the Space and the List new tasks are created in and save it once for the whole project.

Read the setup docsThe docs cover connecting a ClickUp Workspace, the default List, creating tasks and priority mapping.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

Linear and Jira export tickets too. With several connected, Create ticket becomes a menu. GitHub posts pull request checks, Slack receives run summaries and coding agents debug failures over MCP.

LinearIssues the agents find become Linear tickets through one shared project-wide connection.JiraIssues the agents find become Jira tickets through one shared project-wide connection.GitHubThe GitHub App posts checks and comments on every pull request preview.SlackGroup run summaries with a link per run land in a Slack channel.

[04] FAQ

Questions

TesterArmy fills the task with the issue's description, expected versus actual behavior, reproduction steps, a priority mapped from severity, a screenshot link and a link back to TesterArmy, and names the teammate who exported it.

One teammate approves TesterArmy for a ClickUp Workspace and every project member can export tasks, no individual sign-in required. Tasks are created through that account and name the teammate who exported them.

Severity 5 becomes Urgent, 4 High, 3 Normal, and 1 or 2 Low. Issues without a severity get no priority, and the dialog lets you pick another before creating.

Tasks are created in the project's default List, which lives in a Space and optionally a Folder. The dialog can send a single task to another List.

[05] Start with ClickUp

Send the next issue to ClickUp

Connect a ClickUp Workspace once, save the default List, and every teammate can export issues as tasks from the Issues tab.